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"
| Line 4: | Line 4: | ||
<tr><td width="36">[[image:Catnicon.gif]]</td> | <tr><td width="36">[[image:Catnicon.gif]]</td> | ||
<td>UNDER CONSTRUCTION</td> <td width="36">[[image:Catnicon.gif]]</td></tr></table> | <td>UNDER CONSTRUCTION</td> <td width="36">[[image:Catnicon.gif]]</td></tr></table> | ||
| + | |||
</div> | </div> | ||
| Line 13: | Line 14: | ||
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. | 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 | + | == JPA == |
| + | 'NOTE: 'Currently called ORM'' | ||
| − | == MOXy | + | == MOXy == |
| + | ''NOTE: Currently called OXM'' | ||
| − | == | + | == SDO == |
| + | ''NOTE: This component does not yet exist'' | ||
| − | == | + | The Service Data Objects (SDO) component of EclipseLink provides a complete SDO 2.1 implementation as well as many advanced features ... |
| + | |||
| + | == DBWS == | ||
| + | ''NOTE: This component does not yet exist'' | ||
| + | |||
| + | 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. | ||
== Enterprise information Systems (EIS) - ''Does not yet exist'' == | == Enterprise information Systems (EIS) - ''Does not yet exist'' == | ||
| − | == Utils | + | == Utils == |
| + | ''NOTE: This component does not yet exist'' | ||
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 | ||
| Line 40: | Line 50: | ||
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. | ||
| − | == Examples | + | * [[EclipseLink/UserGuide]] |
| + | * File a bug against the Documentation component | ||
| + | * Query for Documentation bugs | ||
| + | |||
| + | == Examples == | ||
| + | |||
| + | ''NOTE: This component does not yet exist'' | ||
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]] | ||
Revision as of 13:42, 14 February 2008
 |
UNDER CONSTRUCTION | |
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
'NOTE: 'Currently called ORM
MOXy
NOTE: Currently called OXM
SDO
NOTE: This component does not yet exist
The Service Data Objects (SDO) component of EclipseLink provides a complete SDO 2.1 implementation as well as many advanced features ...
DBWS
NOTE: This component does not yet exist
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.
Enterprise information Systems (EIS) - Does not yet exist
Utils
NOTE: This component does not yet exist
A set of utilities to assist customer in their development and runtime usage of EclipseLink
- Migration
- Package Re-name utility
- Oracle TopLink Migration Tool
- TopLink Essentials Migration Tool
- Workbench: Standalone mapping tool supporting externalized XML mapping
Documentation
NOTE: This component does not yet exist
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
NOTE: This component does not yet exist
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.