[ 
https://issues.apache.org/jira/browse/FELIX-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre De Rop closed FELIX-730.
-------------------------------


Hi Richard;

I have checked the latest trunk and i still have the same behaviour: If I don't 
provide explicitly the version number, then my bundle is
wired to the system bundle.

I am not sure whether I understand correctly your last message regarding this 
issue: 
Do you assume that, after your last fix, I should be able to be wired to the 
highest version (without providing it) ?
I just wan't to be sure, because the behaviour has not changed since the 
previous trunk version (before your fix).

(please close this ticket if every thing is ok ...)

Best Regards
/pierre



> Can't import highest package version
> ------------------------------------
>
>                 Key: FELIX-730
>                 URL: https://issues.apache.org/jira/browse/FELIX-730
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>         Environment: linux
>            Reporter: Pierre De Rop
>            Assignee: Richard S. Hall
>            Priority: Minor
>             Fix For: felix-1.2.2
>
>         Attachments: framework.log
>
>
> This issue follows up the thread: http://www.mail-archive.com/[EMAIL 
> PROTECTED]/msg02152.html
> - I use jdk 1.6, and all the jdk packages are re-exported from the 
> felix.properties file, with version = 1.6.0
> - I have a bundle "jaxb.jar" which exports package "javax.xml.bind" with 
> version 2.1.4 
> (and the jdk also exports that package, but with version = 1.6.0).
> - a bundle "SipServletDeployer" simply imports "javax.xml.bind" (but without 
> any versions)
> -> the issue is: the bundle "SipServletDeployer" gets wired to the 1.6.0 
> (jdk) version of javax.xml.bind, instead of version 2.1.4.
> (but if I force "version=2.1.4" in  "SipServletDeployer", then it is properly 
> wired to the jaxb.jar bundle).
> Richard; could you please take a look at the log attached to this issue, 
> because I don't think package "javax.xml.bind" is 
> already loaded from system bundle (version 1.6.0) at the time 
> "SipServletDeployer" is loaded ...
> you can grep "javax.xml.bind" from the log file:
> DEBUG: WIRE: 64.0 -> javax.xml.bind.annotation -> 15.0     (bundle 64 is 
> wired to 15 (jaxb.jar) because it imports javax.xml.bind;version=2.1.4
> DEBUG: WIRE: 62.0 -> javax.xml.bind -> 15.0                     (bundle 62 is 
> wired to  15 (jaxb.jar) because it imports javax.xml.bind;version=2.1.4
> DEBUG: WIRE: 30.0 -> javax.xml.bind -> 0                         (but bundle 
> 30 (SipServletDeployer) is wired to jdk (system bundle) because it does not 
> import with v=2.1.4 ...
> etc ...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to