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 "EclipseLink/Features"
(→Object-Relational: JPA) |
(→Object-Relational: JPA) |
||
Line 19: | Line 19: | ||
* DatabasePlatform controlling database specific functionality | * DatabasePlatform controlling database specific functionality | ||
* Internal and external DataSource/JDBC connection access | * Internal and external DataSource/JDBC connection access | ||
− | * [EclipseLink/Features/ORM] | + | * [[EclipseLink/Features/ORM | More Details...]] |
== MOXy: Object-XML/JAXB == | == MOXy: Object-XML/JAXB == |
Revision as of 14:50, 16 August 2007
Contents
Eclipse Persistence Services Project (EclipseLink) Features
This page and its sub-pages list all of the features of EclipseLink and their intended usage. EclipseLink delivers functionality for object-relational, object-XML, and EIS using JCA resource adapter. EclipseLink is focussed on delivering support for leading persistence standards and extensions needed for enterprise application development.
Core Functionality
One of the benefits of using the EclipseLink solution is its core infrastructure shared across multiple persistence services. These capabilities include:
- Common class mapping with customization policies with event callbacks
- Multiple session types with event callbacks
- Transaction Framework tracking entity changes using JDBC transactions or JTA
Object-Relational: JPA
- Object-Relational Mappings with many customizations
- Object Caching Solution
- Multiple Metadata Configuration approaches
- DatabasePlatform controlling database specific functionality
- Internal and external DataSource/JDBC connection access
- More Details...
MOXy: Object-XML/JAXB
- JAXB
Service Data Objects (SDO)
Eclipselink