I have a very simple web application running on Tomcat using Spring 3.0.2, Hibernate 3.5.1, JPA 2, and Derby. I am defining all the capabilities of my database in persistence.xmland just using Spring to inject dependencies. I use the built-in Derby as my database.
Everything works correctly when I define the properties of the driver and the URL persistence.xmlin Hibernate classic mode this way:
<property name="hibernate.connection.driver_class" value="org.apache.derby.jdbc.EmbeddedDriver"/>
<property name="hibernate.connection.url" value="jdbc:derby:webdb;create=true"/>
Problems arise when switching my configuration to the standardized JPA2 properties as follows:
<property name="javax.persistence.jdbc.driver" value="org.apache.derby.jdbc.EmbeddedDriver"/>
<property name="javax.persistence.jdbc.url" value="jdbc:derby:webdb;create=true"/>
Using JPA2 property keys, the application requires a lot of effort with the following exception:
java.lang.UnsupportedOperationException: The user must supply a JDBC connection
Does anyone know why this fails?
. javax... Hibernate, .