Hi,Well this actually has been an issue since karaf-3.0.0. That's when it started exporting javax.annotation. At first it was exported with version "1.1" before it was changed it to "1.2" in karaf-3.0.2.
As soon as a client-bundle actually requires a 1.1 or 1.2 annotation and the javax.annotation-bundle has to be provided this is an issue.
AFAICT there aren't that many javax-specs affected with such a version descrepancy. Putting it in endorsed, doesn't sound too bad, and would work around issues with multiple javax.annotation-bundles present.
kind regards, Christoph On 28/10/14 14:39, Daniel Kulp wrote:
Curiosity question…. CXF imports javax.annotation using a version range of [0.0,2) so it should work with a different versions. If I install CXF, how will this work with the various versions now provided? In particular, if a user bundle providing a CXF service uses the javax.annotation things, is there an easy way to make sure both CXF and the user bundle end up using the same version? For example, if I install CXF first, I assume it would get 1.0 from the JRE. Then I install a the 1.2 bundle, then a user bundle. Would the user bundle get 1.2 and then not properly work with CXF? If I restart the container, would CXF then pick up 1.2? This is beginning to look very complicated and very non-obvious error inducing. I’m almost wondering if it makes more sense to throw 1.2 into endorsed and make sure that’s exported from jre.properties as 1.2.
smime.p7s
Description: S/MIME Cryptographic Signature
