[ 
https://issues.apache.org/jira/browse/FELIX-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633517#action_12633517
 ] 

Richard S. Hall commented on FELIX-730:
---------------------------------------

After discussing this with Tom Watson, I think Felix might be implementing it 
correctly after all. The R4.1 spec states at the end of 3.7 that the preference 
is for "resolved" exporters over unresolved ones. I was originally thinking it 
was "in use" exporters, which would be ones that actually have a wire to them, 
but a "resolved" exporter is simply one that has been previously resolved. The 
system bundle must be resolved, so since the importer matches both, then the 
resolved state of the system bundle gives it higher priority, version number 
has a lower precedence. I will still look into this a little more before 
resolving the issue.

> 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
>            Priority: Minor
>         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