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

 
(35 intermediate revisions by 11 users not shown)
Line 1: Line 1:
 
<div style="float:right;width:300px">
 
<div style="float:right;width:300px">
 +
[http://www.eclipse.org/eclipselink/releases/2.3.0.php EclipseLink 2.3.0 Release]
 
__TOC__
 
__TOC__
 
</div>
 
</div>
  
== Themes ==
+
== EclipseLink 2.3.0 (Indigo) Development ==
  
=== Extensible Entity Types ===
+
Application developers are continuously faced with deploying to larger clusters and application grids as well as public and private clouds with SaaS and PaaS. In order to do this effectively they are challenged with how to address persistence in these environments as well as how to minimize future development costs as they address:
  
As more flexible applications are developed to handle dynamic end user customizations application developers are increasingly challenged with building extensible domain models. In this release EclipseLink will further simplify the development and mapping of these models including storing and leveraging the necessary extension metadata and exposing a domain metamodel that will allow consuming application components to understand the structure of the domain model including extensions and expose it to its consumers.  
+
* Monitoring and Management
 +
* Growing volumes of data using partitioning strategies
 +
* Built in support for end user extensible applications
 +
* Multiple tenant data architectures  
 +
* Application version upgrade
  
=== Deployment Overrides ===
+
While EclipseLink has supported these advanced persistence capabilities in previous releases the Indigo release will focus on simplifying how these are used, educating the community on their use, and supporting their use with documentation and examples.
  
Currently EclipseLink offers great support for flexible mapping using annotations and/or standard and extended XML mapping files where the XML specified mappings can be used to override defaults and annotation specified mappings. In this release this support will be enhanced to allow externally provided configuration and mapping overrides to be used. The intent is to allow greater flexibility through dynamic management where future instances of the application can use overrides from previous versions when stored in any arbitrary metadata storage facility. This functnality will also assist with multi-tenant [http://en.wikipedia.org/wiki/SaaS SaaS] usage where different instances of the application may service different tenants and may require different configuration customizations.
+
== Features ==
  
=== Schema Provisioning and Upgrade ===
+
The above listed themes for this release are translated into the following features.
  
Improve EclipseLink's support for creating a schema on demand including upgrading a schema to support new types and mapped attributes added in new versions of the application. This functionality is targeted at improving support for dynamically handling the upgrade of application components using EclipseLink as well as [http://en.wikipedia.org/wiki/PaaS#Platform PaaS] environments where the application deployment and provisiong cycle may require the creation of a new schema.
+
* JPA
 +
** [[EclipseLink/DesignDocs/340192 | Extensible Domain Models]]
 +
*** [[EclipseLink/Examples/JPA/Extensibility | Example for using Extensible Domain Model]]
 +
** [[EclipseLink/Development/Indigo/Multi-Tenancy | Multi-Tenant Shared Schema]]
 +
*** [[EclipseLink/Examples/JPA/Multitenant | Example]]
 +
** [[EclipseLink/DesignDocs/328404_new | Composite Persistence Units]]
 +
*** [[EclipseLink/Examples/JPA/Composite | Example]]
 +
** [[EclipseLink/DesignDocs/275156 | Extended Stored Procedure and PLSQL Support]]
 +
*** [[EclipseLink/Examples/JPA/PLSQLStoredFunction|Example]]
  
== Schedule==
+
* MOXy
 +
** [[EclipseLink/Development/339371 | Extensible Domain Models]]
 +
*** [[EclipseLink/Examples/MOXy/Extensible | XML Extensions]]
 +
*** Support refresh of JAXBContext metadata
 +
** Mapping Enhancements
 +
*** [[EclipseLink/Examples/MOXy/ElementMappingByAttributeValue | XPath Mapping with Predicates]]
 +
*** [[EclipseLink/Examples/MOXy/MultipleBindingsFiles | Multiple Bindings File Support]]
 +
*** [[EclipseLink/Examples/MOXy/XMLNameTransformer | Customized XML Name Conversions]]
 +
* DBWS
 +
** [[EclipseLink/Examples/DBWS/DBWSComplexArgStoredFunction| EclipseLink DBWS Service based on Stored Function with complex PL/SQL arguments]]
 +
** [[EclipseLink/Examples/DBWS/DBWSOverloadStoredProcedure| EclipseLink DBWS Service based on overloaded Stored Procedure]]
  
    * Indigo M5+1 - Jan 31
+
== Indigo Schedule ==
    * Indigo M6+1 - March 14
+
    * Indigo M7+1 - May 2
+
    * Indigo RC1-4 May 16,23,30 and June 6
+
    * Indigo GA - June 22
+
 
+
== Features ==
+
  
=== JPA ===
+
The [Indigo/Simultaneous_Release_Plan] governs the overall release. The EclipseLink contribution dates to the release are:
  
=== MOXy ===
+
* Indigo M5+1 - Jan 31
 +
* Indigo M6+1 - March 14
 +
* Indigo M7+1 - May 2
 +
* Indigo RC1-4 May 16,23,30 and June 6
 +
* Indigo GA - June 22
  
=== DBWS ===
+
[[Category:EclipseLink|Indigo]]

Latest revision as of 15:02, 24 October 2011

EclipseLink 2.3.0 (Indigo) Development

Application developers are continuously faced with deploying to larger clusters and application grids as well as public and private clouds with SaaS and PaaS. In order to do this effectively they are challenged with how to address persistence in these environments as well as how to minimize future development costs as they address:

  • Monitoring and Management
  • Growing volumes of data using partitioning strategies
  • Built in support for end user extensible applications
  • Multiple tenant data architectures
  • Application version upgrade

While EclipseLink has supported these advanced persistence capabilities in previous releases the Indigo release will focus on simplifying how these are used, educating the community on their use, and supporting their use with documentation and examples.

Features

The above listed themes for this release are translated into the following features.

Indigo Schedule

The [Indigo/Simultaneous_Release_Plan] governs the overall release. The EclipseLink contribution dates to the release are:

  • Indigo M5+1 - Jan 31
  • Indigo M6+1 - March 14
  • Indigo M7+1 - May 2
  • Indigo RC1-4 May 16,23,30 and June 6
  • Indigo GA - June 22

Back to the top