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/OSGi"
< EclipseLink | Development
(→Proposals) |
(→Requirements) |
||
| Line 4: | Line 4: | ||
== Requirements == | == Requirements == | ||
| + | |||
| + | # Make EclipseLink bundles easy to use within other Eclipse projects and RCP applications without hindering the Java (SE/EE) usage | ||
| + | # Ensure that the bundles offer flexibility in their independent usage. The usage of EclipseLink JPA should not force the usage of EclipseLink's JAXB | ||
== Current Status == | == Current Status == | ||
Revision as of 17:20, 15 December 2007
This page is focussed on capturing how EclipseLink will be developed and used for an OSGi (Equinox) environment.
The goal of this effort is to produce OSGi bundles for use in other Eclipse projects and RCP applications. While the focus is on OSGi it is understood that Equinox extensions will be required.
Contents
Requirements
- Make EclipseLink bundles easy to use within other Eclipse projects and RCP applications without hindering the Java (SE/EE) usage
- Ensure that the bundles offer flexibility in their independent usage. The usage of EclipseLink JPA should not force the usage of EclipseLink's JAXB
Current Status
Proposals
Bundles:
- org.eclipse.persistence.foundation
- org.eclipse.persistence.jpa
- org.eclipse.persistence.moxy
- org.eclipse.persistence.sdo