[
https://issues.apache.org/jira/browse/FELIX-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737598#action_12737598
]
Richard S. Hall commented on FELIX-1435:
----------------------------------------
I have committed a fix for this, but I am not completely happy with it. It
attempts to merge fragments before seeing if it is even necessary (i.e., if the
bundle has any dynamic imports). I could simply check to see if it is needed,
but this check already happens internally in the resolver, so it seems like
duplication of effort. I need to think about this some more.
> Resolver does not always resolve a dynamic import to a fragment export
> ----------------------------------------------------------------------
>
> Key: FELIX-1435
> URL: https://issues.apache.org/jira/browse/FELIX-1435
> Project: Felix
> Issue Type: Bug
> Components: Framework, Specification compliance
> Affects Versions: felix-1.8.1
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: felix-2.0.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
