-
Type: Bug
-
Resolution: Done
-
Priority: 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:
- 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.)
- mongodb-driver-sync-VERSION.jar
- mongodb-driver-core-VERSION.jar
- slf4j-api-VERSION.jar
- slf4j-log4j12-VERSION.jar
- log4j-VERSION.jar
- bson-VERSION.jar
- bson-record-codec-VERSION.jar
- 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.