Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-16093

JNDI documentation still refers to legacy java driver

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.3.5, 4.5.1, 4.6.0, 4.4.1, 4.7.0, 4.8.0, 4.9.0
    • Component/s: drivers
    • Labels:

      The page "Connect to MongoDB Using a JNDI Datasource" refers to files or code from the legacy Java driver in a couple of places:

      1. Both the Wildfly and Tomcat instructions say to copy the `mongo-java-driver.jar` file, which was replaced by `mongodb-driver-sync.jar`. For Tomcat at least, there are several other .jar files that need to be copied since this is not an uber jar anymore. (I'm not sure this is a complete list – it doesn't work for me yet.)
        1. mongodb-driver-sync-VERSION.jar
        2. mongodb-driver-core-VERSION.jar
        3. slf4j-api-VERSION.jar
        4. slf4j-log4j12-VERSION.jar
        5. log4j-VERSION.jar
        6. bson-VERSION.jar
        7. bson-record-codec-VERSION.jar
      2. The Tomcat instructions for the `<Resource>` entity specifies the non-legacy factory `com.mongodb.client.MongoClientFactory`, but the legacy resource type `com.mongodb.MongoClient` (I believe this resource type should be `com.mongodb.client.MongoClient`.)

       

      This change applies to all documented versions of the Java documentation

       

      A/C:

      As a user, I can find up to date information on the dependencies needed to connect to JNDI.

            Assignee:
            jordan.smith@mongodb.com Jordan Smith
            Reporter:
            jmclaren@legendpower.com Jason McLaren
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              21 weeks, 5 days ago