Craig L Russell resolved JDO-771.
    Resolution: Fixed

> Update requirement of ConnectionDriverName since JDBC 4 changed requirements
> ----------------------------------------------------------------------------
>                 Key: JDO-771
>                 URL: https://issues.apache.org/jira/browse/JDO-771
>             Project: JDO
>          Issue Type: Improvement
>          Components: api, specification
>    Affects Versions: JDO 3.1
>            Reporter: Andy Jefferson
>            Assignee: Craig L Russell
>            Priority: Minor
>             Fix For: JDO 3.2
> 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+?

This message was sent by Atlassian JIRA

Reply via email to