Community
Participate
Working Groups
>The OSGI enabled Eclipse Virgo 2.1.0 server is now released and supports JSP/Servlet WAR applications (a subset of the EE spec) The spring framework can act as the persistence container to provide a subset of EE functionality on top of the web container. We need to prototype a quickstart EclipseLink JPA based web app and determine if anything different is required on our end - specifically if we need an implementation of ServerPlatform. We likely will treat this SpringSource DM based OSGI server like we do other web-only containers like Tomcat, SpringSource TC(tomcat) and WebSphere CE/Geronimo - using the SE NoServerPlatform.
I had a working implementation on top of Virgo 2.1.0 using some of the older jpa.osgi stuff. I'm stepping through the 3.0.0.M1 package now. The big thing to note, I think, is the javax.persistence difference. The springsource one seems to follow the 'right' verison (e.g. 1.1) but since the EclipseLink javax.persistence is 2.0.3 then it overrides it, providing that it's installed ahead of it. This also means that the javax.persistence will be incompatible with some Aries projects, which use Import-Package: javax.persistence;version="[1.1,2)",... (e.g. in http://www.apache.org/dyn/closer.cgi/aries/org.apache.aries.samples.blog.jpa.eba-0.3.eba).
The Aries example may be lagging behind the Aries JPA code. The pom for the JPA Container contains the following import declaration: <Import-Package> javax.persistence;version="[1.0.0,2.1.0)", javax.persistence.spi;version="[1.0.0,2.1.0)", org.osgi.framework;version="[1.5.0,2.0.0)", </Import-Package> These ranges are compatible with EclipseLink 2.2.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
