[
https://issues.apache.org/jira/browse/FELIX-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-730.
-----------------------------------
Resolution: Fixed
Fix Version/s: felix-1.2.2
Assignee: Richard S. Hall
I will mark this bug as "fixed", although it wasn't really a bug per se, since
the resolver was doing the correct thing. However, I did realize that there was
perhaps some confusion regarding whether the resolver should be keeping track
of "in use" vs "resolved" packages. As a result, I modified the resolver to
make it clear that we are dealing with "resolved" packages and improved some of
the data structure handling that was not previously correct since it was
assuming "in use" semantics. I did uncover a bug in the resolver, but I will
open a new issue for that.
Peirre, if you are satisfied with this, please close this 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
> 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.
