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.
Difference between revisions of "EclipseLink/Components"
(→JPA) |
(→NoSQL) |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
The Eclipse Persistence Services Project (EclipseLink) provides a comprehensive set of persistence infrastructure with a common foundation. The project is divided up into several components addressing the various persistence services and supporting infrastructure to assist consumers in their use of the project. These components are reflected in the source repository and the bug database. | The Eclipse Persistence Services Project (EclipseLink) provides a comprehensive set of persistence infrastructure with a common foundation. The project is divided up into several components addressing the various persistence services and supporting infrastructure to assist consumers in their use of the project. These components are reflected in the source repository and the bug database. | ||
| Line 15: | Line 9: | ||
== JPA == | == JPA == | ||
| − | |||
The Java Persistence API (JPA) of EclipseLink provides a rich object-relational solution delivering a JPA compliant implementation with many advanced capabilities for complex enterprise Java applications. | The Java Persistence API (JPA) of EclipseLink provides a rich object-relational solution delivering a JPA compliant implementation with many advanced capabilities for complex enterprise Java applications. | ||
== MOXy == | == MOXy == | ||
| − | ' | + | |
| + | Mapping Objects to XML components is primarily the EclipseLink JAXB implementation offering additional mapping typoes and options as well as support for externalized (XML) mapping metadata in addition to JAXB's annotation approach. | ||
== SDO == | == SDO == | ||
| − | |||
| − | The Service Data Objects (SDO) component of EclipseLink provides a complete SDO 2.1 implementation | + | The Service Data Objects (SDO) component of EclipseLink provides a complete SDO 2.0.1 implementation. It leverages all of the mapping capabilities of MOXy and the classic object-XML support of the foundation component. Users of EclipseLink SDO can use the provided model generator and runtime with either a static or dynamic model. |
== DBWS == | == DBWS == | ||
| − | |||
The Database Web Services (DBWS) component of EclipseLink will provide the capability to easily expose a back-end data source as a web service with flexible control over the data source access and the XML payload used in the web services operations. | The Database Web Services (DBWS) component of EclipseLink will provide the capability to easily expose a back-end data source as a web service with flexible control over the data source access and the XML payload used in the web services operations. | ||
| − | == | + | == Extensions == |
| − | + | ||
| − | The | + | The Extensions component provides extensions to EclipseLink to support third party APIs. The extensions component classes are packaged into the org.eclipse.persistence.extension_<version>.jar and are not part of the eclipselink.jar to facilitate easier deployment. The goal of the extensions component is to avoid dependencies from the core components on third party APIs, and making it easier for extensions to depend on third party APIs. |
| + | |||
| + | These include: | ||
| + | * [http://www.jgroups.org/ JGroups] - Extension to support cache coordination across the JGroups communication library. | ||
| + | * [http://code.google.com/p/kryo/ Kryo] - Extension to support the Kryo optimized serialization library for cache coordination, and serialized converters. | ||
| + | |||
| + | == NoSQL == | ||
| + | |||
| + | The NoSQL component of EclipseLink delivers persistence functionality for developers to access and manipulate persistent data in object form from non-relational data sources using Java Connector Architecture (JCA) resource adapters. | ||
== Utils == | == Utils == | ||
| − | |||
A set of utilities to assist customer in their development and runtime usage of EclipseLink | A set of utilities to assist customer in their development and runtime usage of EclipseLink | ||
* Migration | * Migration | ||
| − | ** Package Re-name utility | + | ** Package Re-name utility for migration from TopLink Essentials and earlier versions of Oracle TopLink |
| − | + | ||
| − | + | ||
* Workbench: Standalone mapping tool supporting externalized XML mapping | * Workbench: Standalone mapping tool supporting externalized XML mapping | ||
| + | ** ''The workbench is intended for customers migrating from the class Oracle TopLink's ORM and OXM support. It is not intended for customers using JPA.'' | ||
== Documentation == | == Documentation == | ||
| − | |||
| − | |||
The EclipseLink project offers a rich set of documentation maintained on the wiki. This component will enable tracking of bugs and enhancement requests in bugzilla for this content. | The EclipseLink project offers a rich set of documentation maintained on the wiki. This component will enable tracking of bugs and enhancement requests in bugzilla for this content. | ||
| Line 60: | Line 55: | ||
== Examples == | == Examples == | ||
| − | |||
| − | |||
One of the key success criteria of a runtime framework is providing access to a rich set of examples that consumers can try to quickly gain knowledge of how the various persistence services and features work. This component will deliver a comprehensive set of examples maintained and tested for each milestone and release. | One of the key success criteria of a runtime framework is providing access to a rich set of examples that consumers can try to quickly gain knowledge of how the various persistence services and features work. This component will deliver a comprehensive set of examples maintained and tested for each milestone and release. | ||
[[EclipseLink/Examples]] | [[EclipseLink/Examples]] | ||
Latest revision as of 13:08, 17 June 2013
The Eclipse Persistence Services Project (EclipseLink) provides a comprehensive set of persistence infrastructure with a common foundation. The project is divided up into several components addressing the various persistence services and supporting infrastructure to assist consumers in their use of the project. These components are reflected in the source repository and the bug database.
Foundation
The foundation component is primarily the common mapping and runtime persistence infrastructure leveraged by the other components. It also contains the native object-relational and object-XML functionality.
JPA
The Java Persistence API (JPA) of EclipseLink provides a rich object-relational solution delivering a JPA compliant implementation with many advanced capabilities for complex enterprise Java applications.
MOXy
Mapping Objects to XML components is primarily the EclipseLink JAXB implementation offering additional mapping typoes and options as well as support for externalized (XML) mapping metadata in addition to JAXB's annotation approach.
SDO
The Service Data Objects (SDO) component of EclipseLink provides a complete SDO 2.0.1 implementation. It leverages all of the mapping capabilities of MOXy and the classic object-XML support of the foundation component. Users of EclipseLink SDO can use the provided model generator and runtime with either a static or dynamic model.
DBWS
The Database Web Services (DBWS) component of EclipseLink will provide the capability to easily expose a back-end data source as a web service with flexible control over the data source access and the XML payload used in the web services operations.
Extensions
The Extensions component provides extensions to EclipseLink to support third party APIs. The extensions component classes are packaged into the org.eclipse.persistence.extension_<version>.jar and are not part of the eclipselink.jar to facilitate easier deployment. The goal of the extensions component is to avoid dependencies from the core components on third party APIs, and making it easier for extensions to depend on third party APIs.
These include:
- JGroups - Extension to support cache coordination across the JGroups communication library.
- Kryo - Extension to support the Kryo optimized serialization library for cache coordination, and serialized converters.
NoSQL
The NoSQL component of EclipseLink delivers persistence functionality for developers to access and manipulate persistent data in object form from non-relational data sources using Java Connector Architecture (JCA) resource adapters.
Utils
A set of utilities to assist customer in their development and runtime usage of EclipseLink
- Migration
- Package Re-name utility for migration from TopLink Essentials and earlier versions of Oracle TopLink
- Workbench: Standalone mapping tool supporting externalized XML mapping
- The workbench is intended for customers migrating from the class Oracle TopLink's ORM and OXM support. It is not intended for customers using JPA.
Documentation
The EclipseLink project offers a rich set of documentation maintained on the wiki. This component will enable tracking of bugs and enhancement requests in bugzilla for this content.
- EclipseLink/UserGuide
- File a bug against the Documentation component
- Query for Documentation bugs
Examples
One of the key success criteria of a runtime framework is providing access to a rich set of examples that consumers can try to quickly gain knowledge of how the various persistence services and features work. This component will deliver a comprehensive set of examples maintained and tested for each milestone and release.