Community
Participate
Working Groups
The specification has added standardized persistence unit properties. Support must be added for these properties. See http://wiki.eclipse.org/index.php?title=EclipseLink/Development/JPA_2.0/standard_properties
*** Bug 258664 has been marked as a duplicate of this bug. ***
this includes the javax.persistence.query.timeout property
Added URL link to wiki page for tracking requirements/design/issues
Created attachment 126658 [details] Patch that implements standard properties feature Will update the wiki once this patch is committed. The above patch implements "query timeout" and also adds support for javax.persistence properties. JUnit tests are also included. Tested for regression and see no regression.
Created attachment 126893 [details] updated patch with changes suggested by Andrei
Created attachment 127405 [details] Slightly updated patch Removed PessimisticLockTimeoutProp from PropertiesHandler; fixed EntityManagerJUnitTestSuite.testEMFactoryCloseAndOpen
Checked the fix into trunk.
Created attachment 127553 [details] Correction: Rolled back changes to JUnitTestCaseHelper - it's a core (not jpa) testing file, the changes made some core qa tests to fail.
Created attachment 127835 [details] Changed all core tests to use new javax.persistence properties My last patch broke some tests. The reason being that some core test objects were still using the old eclipselink.jdbc.user properties, where some tests expected PersietenceUnitProperties.JDBC_USER. Now all "eclipselink.jdbc.user/password/url/driver" properties in foundation changed to the new "javax.persistence.jdbc.user/password/url/driver" properties. Note that the old properties still left in some jpa tests (performance, memory leak tests) - but there the properties passed directly to createEMF method, which is ok.
Mass update to change fixed in target.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink