Difference between revisions of "EclipseLink/Features"

From Eclipsepedia

Jump to: navigation, search
m (Eclipse Persistence Services Project (EclipseLink) Features)
(Tools and Utilities)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Eclipse Persistence Services Project (EclipseLink) Features =
+
{| cellspacing="1" cellpadding="1" width="100%" border="1" align="center"
 +
|-
 +
|| [[Image:Catnicon.gif]]'''This page is under construction. Content being addressed in ongoing [[EclipseLink/UserGuide|UserGuide]] enhancements '''[[Image:Catnicon.gif]]
 +
|}
  
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 focused on delivering support for leading persistence standards and extensions needed for enterprise application development.
+
__TOC__
  
== Core Functionality ==
+
= Eclipse Persistence Services Project (EclipseLink) Features  =
  
One of the benefits of using the EclipseLink solution is its core infrastructure shared across multiple persistence services.  
+
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 focused on delivering support for leading persistence standards and extensions needed for enterprise application development.  
These capabilities include:
+
  
* Common class mapping with customization policies with event callbacks
+
== Core Functionality  ==
* Multiple session types with  event callbacks
+
* Transaction Framework tracking entity changes using JDBC transactions or JTA
+
* [[EclipseLink/Features/Core | More Details...]]
+
  
== [[EclipseLink/Features/JPA | JPA: Object-Relational]] ==
+
One of the benefits of using the EclipseLink solution is its core infrastructure shared across multiple persistence services. These capabilities include:  
  
* Object-Relational Mappings with many customizations
+
*Common class mapping with customization policies with event callbacks
* Object Caching Solution
+
*Multiple session types with event callbacks
* Multiple Metadata Configuration approaches
+
*Transaction Framework tracking entity changes using JDBC transactions or JTA
* DatabasePlatform controlling database specific functionality
+
*[[EclipseLink/Features/Core|More Details...]]
* Internal and external DataSource/JDBC connection access
+
* [[EclipseLink/Features/JPA | More Details...]]
+
  
== MOXy: Object-XML/JAXB ==
+
== [[EclipseLink/Features/JPA|JPA: Object-Relational]]  ==
  
* JAXB 2.0
+
*Object-Relational Mappings with many customizations
** Annotation based configuration
+
*Object Caching Solution
** Generation of model/schema and mappings starting from XSD or domain model
+
*Multiple Metadata Configuration approaches
** Standard JAXB marshaling and un-marshaling API
+
*DatabasePlatform controlling database specific functionality
* Object-XML Extensions
+
*Internal and external DataSource/JDBC connection access
** Definition of mappings in XML configuration file
+
*[[EclipseLink/Features/JPA|More Details...]]
* [[EclipseLink/Features/MOXy| More Details...]]
+
  
== Service Data Objects (SDO) ==
+
== MOXy: Object-XML/JAXB  ==
 +
 
 +
*JAXB 2.0
 +
**Annotation based configuration
 +
**Generation of model/schema and mappings starting from XSD or domain model
 +
**Standard JAXB marshaling and un-marshaling API
 +
*Object-XML Extensions
 +
**Definition of mappings in XML configuration file
 +
*[[EclipseLink/Features/MOXy|More Details...]]
 +
 
 +
== Service Data Objects (SDO) ==
  
 
Service Data Objects (SDO) offers a standardized way to deal with XML data through a standardized object model. This approach to persistence allows developers to more easily move their model through a Service Oriented Architecture moving in and out of XML while also managing a record of changes made to the data objects.  
 
Service Data Objects (SDO) offers a standardized way to deal with XML data through a standardized object model. This approach to persistence allows developers to more easily move their model through a Service Oriented Architecture moving in and out of XML while also managing a record of changes made to the data objects.  
  
* [[EclipseLink/Features/SDO | More Details...]]
+
*[[EclipseLink/Features/SDO|More Details...]]
  
== EIS using JCA ==
+
== EIS using JCA ==
  
 
EclipseLink also supports mapping to non-relational data sources using the JavaEE Connector Architecture (JCA).  
 
EclipseLink also supports mapping to non-relational data sources using the JavaEE Connector Architecture (JCA).  
  
* Mapping to JCA adapter interchange leveraging core descriptor capabilities
+
*Mapping to JCA adapter interchange leveraging core descriptor capabilities  
** Mapping to JCA's Common Connector Interface (CCI) API
+
**Mapping to JCA's Common Connector Interface (CCI) API  
** Mapping to XML interchange documents using MOXy
+
**Mapping to XML interchange documents using MOXy  
* Support for leveraging the core sessions, caching, and transaction capabilities
+
*Support for leveraging the core sessions, caching, and transaction capabilities  
* [[EclipseLink/Features/EIS | More Details...]]
+
*[[EclipseLink/Features/EIS|More Details...]]
  
== Tools and Utilities ==
+
== Tools and Utilities ==
  
Within the EclipseLink project there are also a number of utilities that can be used during development to improve productivity.
+
Within the EclipseLink project there are also a number of utilities that can be used during development to improve productivity.  
  
* [[EclipseLink/Features/Workbench | Workbench]]
+
*[[EclipseLink/Features/Workbench|Workbench]]  
* Migration Utilities
+
*Migration Utilities  
** Package Rename Utility
+
**Package Rename Utility
* Web Client
+
  
 +
<br> See [[EclipseLink/UserGuide/Overview of EclipseLink Development Tools (ELUG)|Overview of EclipseLink Development Tools]] in the [[EclipseLink/UserGuide|EclipseLink User's Guide]] for more information.
  
See [[EclipseLink/UserGuide/Overview of EclipseLink Development Tools (ELUG)|Overview of EclipseLink Development Tools]] in the [[EclipseLink/UserGuide|EclipseLink User's Guide]] for more information.
+
[[Category:EclipseLink|Features]]

Latest revision as of 09:01, 18 October 2011

Catnicon.gifThis page is under construction. Content being addressed in ongoing UserGuide enhancements Catnicon.gif

Contents


[edit] 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 focused on delivering support for leading persistence standards and extensions needed for enterprise application development.

[edit] 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
  • More Details...

[edit] JPA: Object-Relational

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

[edit] MOXy: Object-XML/JAXB

  • JAXB 2.0
    • Annotation based configuration
    • Generation of model/schema and mappings starting from XSD or domain model
    • Standard JAXB marshaling and un-marshaling API
  • Object-XML Extensions
    • Definition of mappings in XML configuration file
  • More Details...

[edit] Service Data Objects (SDO)

Service Data Objects (SDO) offers a standardized way to deal with XML data through a standardized object model. This approach to persistence allows developers to more easily move their model through a Service Oriented Architecture moving in and out of XML while also managing a record of changes made to the data objects.

[edit] EIS using JCA

EclipseLink also supports mapping to non-relational data sources using the JavaEE Connector Architecture (JCA).

  • Mapping to JCA adapter interchange leveraging core descriptor capabilities
    • Mapping to JCA's Common Connector Interface (CCI) API
    • Mapping to XML interchange documents using MOXy
  • Support for leveraging the core sessions, caching, and transaction capabilities
  • More Details...

[edit] Tools and Utilities

Within the EclipseLink project there are also a number of utilities that can be used during development to improve productivity.

  • Workbench
  • Migration Utilities
    • Package Rename Utility


See Overview of EclipseLink Development Tools in the EclipseLink User's Guide for more information.