[FELIX-1435] Resolver does not always resolve a dynamic import to a fragment export

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: framework-1.8.1
• Fix Version/s: framework-2.0.0
• Component/s: Framework, Specification compliance
• Assignee: Richard S. Hall
• Reporter: Richard S. Hall
• Created: 31/Jul/09 16:51
• Updated: 27/Aug/09 14:51
• Resolved: 27/Aug/09 14:51

Description

Packages exported by fragments are not always seen by bundles dynamically importing them. For example, consider the following scenario:

Bundle A dynamically imports some package foo and is resolved, but no other bundles are present. Now a host and fragment are installed (but not resolved) where the fragment exports package foo. If A tries to access a class in foo, it will not get dynamically wired to the package, since the host/fragment pair will not be resolved.

If the host/fragment pair were installed prior to A being resolved, it does work, but this is more by accident than design. We need to explicitly attempt to resolve fragments during dynamic import resolution.