[JAVA-2073] Deprecate DBObject-decoding related constructors and methods that take a DBCollection in favor of ones that takes no arguments Created: 05/Jan/16 Updated: 18/Mar/16 Resolved: 18/Mar/16 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | API |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Now that the DBRef class no longer depends on the DB/DBCollection classes, there is no longer need to pass DBCollection down through the various DBObject-decoding related methods and constructors. These methods and constructors can be deprecated in favor of overloaded ones that don't take a DBCollection |
| Comments |
| Comment by Jeffrey Yemin [ 18/Mar/16 ] |
|
All the DBRef constructors that took a DB were deprecated in 2.x and removed in 3.0. All the decoder-related methods that take a DBCollection reference are defined in public interfaces that third parties may have implemented. We should not add methods to those interfaces to avoid breaking those applications. |