I am trying to run a simple test bundle, which uses Eclipselink on Apache
Felix, however due to dependencies I had to install the bundle
org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar, because I got the error:
however when I install the bundle
I got the following error:
ERROR: Error starting
(org.osgi.framework.BundleException: Activator start error in bundle
org.eclipse.osgi.framework.internal.core.SystemBundleActivat or cannot be
cast to org.osgi.framework.BundleActivator
at org.apache.felix.framework.Felix.createBundleActivator(Felix .java:3350)
It seems that eclipselink runs only on Eclipse equinox? Can anybody
> I am trying to run a simple test bundle, which uses Eclipselink on Apache
> Felix, however due to dependencies I had to install the bundle
> org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar, because I got the error:
Can you provide the stack? You're probably deploying the Equinox JPA
bundle which you shouldn't do when running on Felix.
> It seems that eclipselink runs only on Eclipse equinox? Can anybody
> confirm that?
EclipseLink works great on Felix and Sun has been using it in GlassFish V3
(running on Felix) for some time. The EclipseLink team is working with
the GlassFish team to ensure it works well because EclipseLink is the JPA
2.0 reference implementation and will ship in GlassFish as a component in
the Java EE 6 reference implementation stack.
It looks like we are getting the version of QName that is included in the
JDK from Equinox. It is worth filing a bug for this.
We are in the middle of a transition to use BND to generate our manifests.
When that transition is complete, issues like this should go away.
I am not familiar with Felix configuration, but if there is a way to
configure it to allow QName to be part of the system, that would be one
Otherwise, it is probably a matter of hacking org.eclipse.persistence.core
to import javax.xml.namespace. (if you do not have a bundle that exports
it, our javax.xml.stream_1.0.1.v200903100845.jar does)