[
https://issues.apache.org/jira/browse/FELIX-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408691#comment-13408691
]
Richard S. Hall commented on FELIX-3587:
----------------------------------------
Interesting issue. Yes, it can be smart enough, but it would actually have to
run the resolver first. Currently, it special cases framework extensions
meaning that they don't run through the resolve process like normal bundles.
This would require some thought, but perhaps ultimately what would be the best
approach is to simply treat them like normal bundles and don't attach the
fragment to the system bundle until the resolver indicates it is needed.
> Uses constraint violation due to framework extension bundle
> -----------------------------------------------------------
>
> Key: FELIX-3587
> URL: https://issues.apache.org/jira/browse/FELIX-3587
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Reporter: Sahoo
>
> There seems to be an issue with framework extension bundle and I have not
> checked the spec yet. Felix allows extension bundle to be attached at
> runtime, but that can sometimes lead to uses constraint violation if a
> package exported by the framework extension is also exported by some other
> regular bundle and that package from regular bundle is in use. A
> refreshPackages solves the issue, but that seems to be putting the onus on
> user. Can the framework be smart enough to not attach an extension bundle to
> host when it sees that an extension is exporting a package which is already
> in use?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
