Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "RT/Indigo"
< RT
(→Highlights) |
|||
| Line 20: | Line 20: | ||
* Multitenant JPA entities with shared tables | * Multitenant JPA entities with shared tables | ||
| − | * | + | ** Development of SaaS solutions has now been made easier. EclipseLink JPA can dynamically manage persistent entities for different tenants using shared tables (AKA striped). EclipseLink will limit the result of all database operations to the rows available to a given tenant. |
| + | * On-the-fly extended mappings with external metadata source support | ||
| + | ** Application developers using EclipseLink JPA and MOXy (JAXB) can now build models which support storage of extended values. The extended values are enabled through JPA mappings which can be defined statically or on-the-flt using an external metadata source. | ||
Revision as of 09:54, 6 June 2011
Eclipse RT - Indigo Highlights
Contents
Eclipse Communication Framework (ECF) 3.5.1/Indigo
Highlights
- Compliant implementations of OSGi 4.2 Remote Service and Remote Service Admin standards
- OSGi Remote Services on Felix
- New XMLRPC Remote Services Provider
- Remote Services Documentation and Examples
EclipseLink 2.3.0/Indigo
Highlights
- Multitenant JPA entities with shared tables
- Development of SaaS solutions has now been made easier. EclipseLink JPA can dynamically manage persistent entities for different tenants using shared tables (AKA striped). EclipseLink will limit the result of all database operations to the rows available to a given tenant.
- On-the-fly extended mappings with external metadata source support
- Application developers using EclipseLink JPA and MOXy (JAXB) can now build models which support storage of extended values. The extended values are enabled through JPA mappings which can be defined statically or on-the-flt using an external metadata source.