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.

-- 
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com



> On Oct 27, 2014, at 4:39 AM, Christoph Gritschenberger 
> <[email protected]> wrote:
> 
> Actually all Java SE versions lack the "java.annotation.ManagedBean"
> that was added in 1.1.
> 
> I now changed the versions to 1.0 for JRE 6, 7, and 8.
> 
> I applied the fix to master and karaf-3.0.x
> 
> kind regards,
> Christoph
> 
> On 23/10/14 11:56, jsnharris wrote:
>> I changed the javax.annotation version in the etc/jre.properties to 1.1 and
>> then added the javax.annotation 1.2 bundle to my Karaf installation and the
>> annotation I need is accessed correctly. If the 1.1 versions are still
>> available for other bundles to use and as 1.1 is in SE, this would appear to
>> be the correct way forward (assuming EE versions are not to be part of
>> standard JRE Karaf settings) 
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://karaf.922171.n3.nabble.com/javax-annotation-1-2-0-and-KARAF-2660-tp4036056p4036090.html
>> Sent from the Karaf - Dev mailing list archive at Nabble.com.
>> 
> 
> 

Reply via email to