My earlier claims of success were overly optimistic. Just getting
everything to load into osgi was one hurdle, but getting jaxb running is a
completely different story.
With the configuration mentioned below,
g! lb | grep -i jax
65|Active | 30|jaxb-api (2.2.11)
66|Active |
Forgot to mention, I did try the JAXB version 2.1.0 that Steffan
recommended.
This rippled through my application code and got to the point where it
would no longer build with a versions so old of some of the dependencies.
I wasn’t able to locate version 2.1.0 for all components either.
Is
hello bruce.
this can become tricky. my recommendation was to do not deploy any JAXB bundle,
but to use the version embedded in the JDK and make sure the system bundle
exports its packages as well. additionally JAXB is not fully OSGi-compatible
concerning class loading, so some additional
Thanks for the hints Stephan. They got me going in the right direction.
My problems went away after I added these to my launchpad¹s list.xml:
bundle
groupIdjavax.xml.bind/groupId
artifactIdjaxb-api/artifactId
version2.2.11/version
/bundle
bundle
