Difference between revisions of "EclipseLink/Development/JPA 2.0/standard properties"

From Eclipsepedia

Jump to: navigation, search
(Functional Requirements)
(Summary)
Line 18: Line 18:
 
In JPA 2.0 the specification has defined standard persistence unit properties for JDBC setting.  These properties will need to be supported
 
In JPA 2.0 the specification has defined standard persistence unit properties for JDBC setting.  These properties will need to be supported
  
See JPA 2.0 ED section [https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_JCP-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=persistence-2.0-pr-oth-JSpec@CDS-CDS_JCP 7.2.1.7] (previously 6.2.1.7) for details.
+
See JPA 2.0 PR section [https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_JCP-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=persistence-2.0-pr-oth-JSpec@CDS-CDS_JCP 7.2.1.7] (previously ED 6.2.1.7) for details.
  
 
* Java EE and SE Properties
 
* Java EE and SE Properties

Revision as of 14:53, 2 February 2009

JPA 2.0: Standardized Properties

JPA 2.0 Root | bug 249023

Date Committer(s) Description
Feb 2, 2009 dclarke Initial feature template

Summary

In JPA 2.0 the specification has defined standard persistence unit properties for JDBC setting. These properties will need to be supported

See JPA 2.0 PR section 7.2.1.7 (previously ED 6.2.1.7) for details.

  • Java EE and SE Properties
    • javax.persistence.query.timeout — value in seconds for query timeout
  • Java SE Properties
    • javax.persistence.jdbc.driver — fully qualified name of the driver class
    • javax.persistence.jdbc.url — driver-specific URL
    • javax.persistence.jdbc.user — username used by database connection
    • javax.persistence.jdbc.password — password for database connection validation

Work Estimate

  1. Develop model for testing access type settings
    approx 2 days
  2. Update processing
    approx 2 days

Functional Requirements

  • Support using new standard property names
  • Support using existing eclipselink.jdbc properties as completely interchangeable with standard ones
  • Add these properties to EntityManagerFactory.getSupportedProperties() and EntityManager.getSupportedProperties()

Design

Documentation

Testing

Open Issues

  1. Deprecation of existing properties
    • Backwards compatibility?
    • Forward Migration?
    • When should we finally remove the eclipselink.* properties?