[
https://issues.apache.org/jira/browse/ARIES-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468098#comment-13468098
]
John Ross commented on ARIES-868:
---------------------------------
RFC 191 in CPEG will enhance the Weaving Hook Service specification so that
dynamic package imports in their final state may be observed prior to any
updates to the bundle wiring. Subsystems will be able to use this information
in order to update the sharing policies in time to let the capabilities
through. This will address woven dependencies but not the DynamicImport-Package
header.
> Subsystem support for woven package dependencies
> ------------------------------------------------
>
> Key: ARIES-868
> URL: https://issues.apache.org/jira/browse/ARIES-868
> Project: Aries
> Issue Type: Improvement
> Components: Subsystem
> Reporter: Mark Nuttall
> Assignee: Mark Nuttall
>
> We need a mechanism to support woven package dependencies within subsystems.
> For example, when running on Equinox 3.7+ the proxy code weaves a dependency
> on org.apache.aries.proxy.weaving.WovenProxy into application code. This
> prevents blueprint-managed subsystems from starting unless a bundle
> explicitly imports the org.apache.aries.proxy.weaving package, which should
> not be necessary. JPA is worse, in that multiple, and "harder to know"
> package dependencies are woven in.
> Investigate mechanisms for informing the SubsystemResolverHook about woven
> packages so that they can be permitted to resolve against the parent
> subsystem.
> Develop one or more itests: for example, one that shows blueprint working in
> a subsystem on Equinox 3.8 without explicitly stating woven package
> dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira