[JAVA-4777] Document that CodecRegistry instances configured by the application are treated as CodecProvider Created: 17/Oct/22 Updated: 28/Oct/23 Resolved: 25/Oct/22 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Codecs |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.0 |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Documentation Changes: | Not Needed | ||||||||
| Description |
|
All instances of CodecRegistry configured by the application, via MongoClientSettings or withCodecRegistry method on MongoDatabase or MongoCollection are actually wrapped by the driver in another CodecRegistry, so effectively the application-provided instances are used only as a CodecProvider. This should be documented clearly, as it's confusing to both users and to driver developers. |
| Comments |
| Comment by Githook User [ 25/Oct/22 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Document that CodecRegistry instances configured by the application a… (#1020)
|
| Comment by Jeffrey Yemin [ 17/Oct/22 ] |
|
This is seen as a less disruptive change than JAVA-4774. |