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/Development/Spring"
(New page: This page is intended to capture the strategy for supporting Spring in EclipseLink. '''STATUS: PROPOSAL''' == Spring Integration == At present the Spring Framework ships with support fo...) |
(No difference)
|
Latest revision as of 13:59, 18 December 2007
This page is intended to capture the strategy for supporting Spring in EclipseLink.
STATUS: PROPOSAL
Contents
Spring Integration
At present the Spring Framework ships with support for Oracle TopLink's native object-relational capabilities as well as with TopLink Essentials's JPA support. In order to enable customers to use EclipseLink within Spring support for EclipseLink's JPA and possible its native ORM need to be added.
JPA Vendor Adapter & Dialect
An adapter and dialect need to be contributed to the Spring Framework to support EclipseLink.
Native ORM Support
This work is being deferred while the new XML metadata format for EclipseLink JPA/ORM is defined (Bug 200040)
Testing
What testing will we do in EclipseLink to ensure we remain compatible with the Spring Framework during our development as well as with their development.
Spring OSGi
Whith EclipseLink's planned support for OSGi/Equinox what should we be doing with Spring OSGi?
Examples
What examples should we make available or should we contribute examples to the Spring Framework distribution?
Additional Integration
Beyond integrating within Spring for JPA/ORM usage additional persistence services may be usable both by end users as well as within the Spring framework.
- MOXy: JAXB
- SDO
- DBWS