Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-4777

Document that CodecRegistry instances configured by the application are treated as CodecProvider

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 4.8.0
    • Affects Version/s: None
    • Component/s: Codecs
    • None
    • Fully Compatible
    • Not Needed

      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.

            Assignee:
            jeff.yemin@mongodb.com Jeffrey Yemin
            Reporter:
            jeff.yemin@mongodb.com Jeffrey Yemin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: