Jeff,
EclipseLink 1.0 supported usage within Equinox.
The
functionality included:
- A
customization to JPA so that it allowed implementations could register their
existence dynamically and listen for new bundles that contained JPA
persistence units
- A
fragment that allows EclipseLink to byte code weave these persistence unit's
entities as they are loaded based on the provided mapping
metadata
- An
RCP Example illustrating EclipseLink JPA in an Equinox environment- http://wiki.eclipse.org/EclipseLink/Examples/OSGi/LazyLoadingRCP
- Test
cases and packaging/class-loader fixes to ensure our MOXy and SDO services
would work with Equinox as well
- Packaging of bundles in a ZIP download
For
this 1.1 release we have maintained the same level of functionality and have
addressed ~9 bugs reported by users of EclipseLink JPA with
Equinox.
For
the EclipseLink 2.0 release in Galileo we will need to take this Equinox support
further ensuring P2 packaging, automated testing, and additional
examples.
Doug
I'm ok with the
release but would like to know more about the status of Equinox and OSGi
integration and adoption. "Equinox" does not appear at all in the slides
and "OSGi" appears once. What moves have been made to increase the
integration with and adoption of Equinox? Is that work done and I missed
it?
Jeff
Douglas Clarke wrote:
Fellow RT-PMC Members,find attached the EclipseLink 1.1 release we are planning for mid-February. We are seeking PMC approval to proceed with our release.have already completed the review and approval of our IP Log for this release.http://wiki.eclipse.org/EclipseLink/IPLog _______________________________________________mailing listrt-pmc@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/rt-pmc
|