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/2.4.0"

m (Features)
 
(22 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
= EclipseLink 2.4.0 Development Plans =
 
= 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 scheduled for fall/winter 2011.
+
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.
 +
 
 +
== JVM ==
 +
 
 +
We will update the minimum VM-level for EclipseLink 2.4.0 from JDK 1.5 to JDK 1.6.  See:
 +
 
 +
https://bugs.eclipse.org/bugs/show_bug.cgi?id=377681
 +
 
  
 
== Infrastructure ==
 
== Infrastructure ==
  
 
* Build
 
* 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.  
+
** '''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.
  
 
== Features ==
 
== Features ==
  
 
* JPA
 
* JPA
** '''Enhanced Schema Provisioning''':  Schema upgrade to handle application version upgrades. Upon request the Schmea will be extended to add additional tables, columns, indexes.  
+
** [[EclipseLink/Development/2.4.0/JPA-RS | '''JPA-RS''']]: An easy to use RESTful interface for interacting with JPA persistence units and EJB session bean methods. {{bug|377024}}
** '''MetadataSource support for PU Properties''': 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.
+
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=338610 Some JPA 2.1 features for Java EE 7]
** ''' JPA 2.1''': Provide early access to some of the JPA 2.1 defined features. This will dependend on the progres sthe expert group makes.
+
** '''Multi-tenancy - ''' [[DesignDocs/Multi-Tenancy/TablePerTenant | '''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.
 +
** [[EclipseLink/DesignDocs/371950 | '''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.
 +
*** [[EclipseLink/Development/2.4.0/PU_Props_MetadataSource]]
 
** '''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.
 
** '''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.
 +
** [[EclipseLink/DesignDocs/356812 | ER 356812: Database Change Event Cache Invalidation]]
 +
** [[EclipseLink/DesignDocs/350484 | ER 350484: Cache indexes]]
 +
** [[EclipseLink/DesignDocs/312146 | ER 312146: Enhanced JPQL]]
 +
** [[EclipseLink/DesignDocs/362899 | ER 362899: Support NoSQL Databases]]
 +
 
* MOXy
 
* MOXy
** [http://wiki.eclipse.org/EclipseLink/DesignDocs/350483 '''Object-JSON''' Mapping support]
+
** [[EclipseLink/DesignDocs/350483 | '''Object-JSON Mapping support''']]: Ability to convert objects to/from JSON documents.
 +
*** Simplifies creation of RESTful services - JAX-RS accepts both XML and JSON messages
 +
*** Same flexibility as current object-to-XML mapping support  
 +
*** No additional compile-time dependencies other than standard JAXB APIs
 +
*** Simplified usage with JAX-RS APIs
 +
**[[EclipseLink/Development/359251 | '''JAXB RI compatible functionality''']]: Support for additional JAXB properties currently supported by the JAXB RI that are above and beyond the spec.
 +
*** Namespace Prefix Mapping: Control declarations of namespace URIs and what prefixes they will be bound to
 +
*** @XmlLocation: Specify a property on JAXB object to indicate object's XML location
 +
*** IDResolver: Override the ID/IDREF processing of the JAXB runtime
 +
*** IdentString: Customize the indents in the marshalled XML document
 +
*** CharacterEscapeHandler: Customize the escaping of special characters
 +
*** XML Declaration Control: JAXB 1.0 property replaced by Marshaller.JAXB_FRAGMENT in JAXB2.0
 +
*** AccessorFactory property: Control access to class fields and properties
 +
*** Cyclic references: Control how JAXB handles a cyclic reference in an object model when marshalling to XML
 +
**[[EclipseLink/Examples/REST | '''Creation of RESTful services using MOXy & JPA''']]: A step-by-step guide on how to use EclipseLink 2.4 functionality to create these services
 
* DBWS
 
* DBWS
** [http://wiki.eclipse.org/EclipseLink/Development/DBWS/ParseDDLforMetadata '''Parse DDL to extract database metadata'''].  Change the way type metadata is accessed by DBWSBuilder, providing support for the following enhancement requests
+
** [http://wiki.eclipse.org/EclipseLink/Development/DBWS/ParseDDLforMetadata '''Parse DDL to extract database metadata'''].  Change the way type metadata from Oracle D/B is accessed by DBWSBuilder, providing support for the following key enhancement requests
*** 325124 DBWSProvider does not handle package REF CURSOR
+
*** 325124 - DBWS support for weakly-typed package REF CURSOR  
*** 339721 DBWS should support strongly-typed package REF CURSOR
+
 
*** 339909 - DBWS should support optional argument queries
 
*** 339909 - DBWS should support optional argument queries
*** 329435 - DBWS does not handle %ROWTYPE mix of PL/SQL types and JDBC Advanced types  
+
*** 329435 - DBWS support for Anchored types (%ROWTYPE, %TYPE) 
** DBWS Generation of JAX-WS Web Services.
+
** 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
 +
 
 +
 
 +
 
 +
[[Category:EclipseLink|Development/2.4.0]]

Latest revision as of 23:37, 20 June 2012

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.

JVM

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

https://bugs.eclipse.org/bugs/show_bug.cgi?id=377681


Infrastructure

  • 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.

Features

  • JPA
    • JPA-RS: An easy to use RESTful interface for interacting with JPA persistence units and EJB session bean methods. bug 377024
    • Some JPA 2.1 features for Java EE 7
    • 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.
    • 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
    • Object-JSON Mapping support: Ability to convert objects to/from JSON documents.
      • Simplifies creation of RESTful services - JAX-RS accepts both XML and JSON messages
      • Same flexibility as current object-to-XML mapping support
      • No additional compile-time dependencies other than standard JAXB APIs
      • Simplified usage with JAX-RS APIs
    • JAXB RI compatible functionality: Support for additional JAXB properties currently supported by the JAXB RI that are above and beyond the spec.
      • Namespace Prefix Mapping: Control declarations of namespace URIs and what prefixes they will be bound to
      • @XmlLocation: Specify a property on JAXB object to indicate object's XML location
      • IDResolver: Override the ID/IDREF processing of the JAXB runtime
      • IdentString: Customize the indents in the marshalled XML document
      • CharacterEscapeHandler: Customize the escaping of special characters
      • XML Declaration Control: JAXB 1.0 property replaced by Marshaller.JAXB_FRAGMENT in JAXB2.0
      • AccessorFactory property: Control access to class fields and properties
      • Cyclic references: Control how JAXB handles a cyclic reference in an object model when marshalling to XML
    • Creation of RESTful services using MOXy & JPA: A step-by-step guide on how to use EclipseLink 2.4 functionality to create these services
  • DBWS
    • Parse DDL to extract database metadata. Change the way type metadata from Oracle D/B 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