Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

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

(Standardized Properties)
(Functional Requirements)
Line 39: Line 39:
  
 
* Support using new standard property names
 
* Support using new standard property names
* Support using existing eclipselink.jdbc properties  
+
* Support using existing eclipselink.jdbc properties as completely interchangeable with standard ones
 +
* Implement EntityManagerFactory.getSupportedProperties() and EntityManager.getSupportedProperties()
  
 
== Design ==
 
== Design ==

Revision as of 14:27, 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 ED section 7.2.1.7 (previously 6.2.1.7) for details.

  • Java EE and SE Properties
    • javax.persistence.lock.timeout — value in seconds for pessimistic lock timeout
    • 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
  • Implement 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?

Back to the top