[JDO-771] Update requirement of ConnectionDriverName since JDBC 4 changed requirements

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: JDO 3.1
• Fix Version/s: JDO 3.2
• Component/s: api, specification
• Assignee: Craig L Russell
• Reporter: Andy Jefferson
• Created: 22/Dec/17 14:19
• Updated: 17/Feb/22 19:54
• Resolved: 22/Feb/18 17:38

Description

JDBC 4.0 changed the requirement for specifying a JDBC driver name. Previously an application had to load the class to register the driver by use of Class.forName.
All JDBC 4.0+ drivers should register themselves. See
https://community.oracle.com/docs/DOC-983612

This likely means that a JDO provider will not require the javax.jdo.option.ConnectionDriverName to be supplied.
DataNucleus (v5.1.5+) certainly doesn't require it, and only previously used it for loading the driver as per previous JDBC semantics.

This is only referred to in section 11.1 and Appendix G of the spec that I can see. Perhaps we can omit it in JDO 3.2+, particularly as the JRE in use will require JDBC v4+?