Skip to main content
Jump to: navigation, search


< EclipseLink‎ | Development
Revision as of 10:51, 27 April 2012 by (Talk | contribs) (Features)

EclipseLink 2.4.0 Development Plans

This page is a working document for what is being planned and developed for EclipseLink 2.4.0, which is part of the Juno coordinated release shipping in June of 2012.


We will update the minimum VM-level for EclipseLink 2.4.0 from JDK 1.5 to JDK 1.6. See:


  • Build
    • Tycho/Maven Migration Incorporate the use of Tycho to generate OSGi bundles using a manifest-first methodology. This will remove the need for BND, but will rely heavily upon developers properly maintaining the manifest files.
  • SCM
    • Git Migration Move existing SVN repository to Git. Actual migration will occur post-release, but follow-patches will be developed in Git.


  • JPA
    • JPA-RS: An easy to use RESTful interface for interacting with JPA persistence units and EJB session bean methods. bug 377024
    • Multi-tenancy - Table per Tenant: The goal of this feature is to allow multiple application tenants to have a their own individual table per tenant. Table per tenant entities can be mixed with other multitenant types within the same persistence unit.
    • Metadata caching: Caching the metadata project so that the setup can avoid costs associated with reading in multiple orm.xml and annotation processing on entities within a persistence unit to rebuild it unnecessarily.
    • [[EclipseLink/DesignDocs/368365 | Enhanced Schema Provisioning: Schema upgrade to handle application version upgrades. Upon request the Schmea will be extended to add additional tables, columns, indexes.
    • MetadataSource support for PU Properties: bug 373120 During the bootstrap of a JPA persistence unit the Metadatasource will provide additional PU properties that can come from an external source to customize the PU properties used in the EntityManagerFactory creation.
    • Gemini JPA: With the Gemini JPA 1.0 release scheduled to come out this summer the current solution available (which we have deprecated) need to be fully transitioned to leverage the Gemini solutions. This will involve updates or migration of examples but may also involve a coordinated Gemini release if feature work is included.
    • ER 356812: Database Change Event Cache Invalidation
    • ER 350484: Cache indexes
    • ER 312146: Enhanced JPQL
    • ER 362899: Support NoSQL Databases
  • MOXy
  • DBWS
    • Parse DDL to extract database metadata. Change the way type metadata is accessed by DBWSBuilder, providing support for the following key enhancement requests
      • 325124 - DBWS support for weakly-typed package REF CURSOR
      • 339909 - DBWS should support optional argument queries
      • 329435 - DBWS support for Anchored types (%ROWTYPE, %TYPE)
    • Other enhancements
      • 326953 - Batch SQL operations
      • 353417 - Non-associative PL/SQL collections
      • 363515 - PL/SQL scalar argument types
      • 366204 - Handle mix of PL/SQL and advanced JDBC types withing a stored procedure/function

Back to the top