[DOCS-16093] JNDI documentation still refers to legacy java driver Created: 02/May/23 Updated: 07/Dec/23 Resolved: 07/Dec/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | drivers |
| Affects Version/s: | 4.3.5, 4.5.1, 4.6.0, 4.4.1, 4.7.0, 4.8.0, 4.9.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jason McLaren | Assignee: | Jordan Smith |
| Resolution: | Done | Votes: | 0 |
| Labels: | bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 weeks, 2 days ago |
| Epic Link: | DOCSP-8754 |
| Description |
|
The page "Connect to MongoDB Using a JNDI Datasource" refers to files or code from the legacy Java driver in a couple of places:
This change applies to all documented versions of the Java documentation
A/C:
|
| Comments |
| Comment by Jordan Smith [ 28/Nov/23 ] |
| Comment by Mike Woofter [ 01/Sep/23 ] |
|
Per Jeff, "slf4j and log4j shouldn’t need to be mentioned, since they were not part of the mongo-java-driver uber jar. The rest look right." |