[
https://issues.apache.org/jira/browse/ARIES-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830672#comment-15830672
]
ASF subversion and git services commented on ARIES-1666:
--------------------------------------------------------
Commit 1779530 from [email protected] in branch 'aries/trunk'
[ https://svn.apache.org/r1779530 ]
[ARIES-1666] Sharing policy is importing from requirements not included
as part of the subsystem
Change-Id: I67aad238c2ead853a447031767fa10c544b0d676
Signed-off-by: Thomas Watson <[email protected]>
> Sharing policy is importing from requirements not included as part of the
> subsystem
> -----------------------------------------------------------------------------------
>
> Key: ARIES-1666
> URL: https://issues.apache.org/jira/browse/ARIES-1666
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Reporter: Thomas Watson
>
> When resolving a subsystem the implementation uses the Resolver service to
> determine the subsystem's dependencies. For application type subsystems this
> causes the sharing policy to be computed according to the wires returned by
> the resolver.
> The subsystems implementation is doing a 'full' resolve to do this. This
> includes re-resolving bundles already resolved in the system repository as
> part of the subsystem resolution or installation process. As a result the
> resolution map used to calculate the import sharing policy contains wires for
> many resources that are not considered as part of the subsystem content. But
> the import policy is updated with the requirements for all wires which do not
> get wired to a provider contained in the subsystem.
> This results in a explosion of filters in the equinox region edge which
> connects the subsystem region to its parent region. This is bad for several
> reasons. 1) may give access to things that the subsystem should not have
> access to 2) will slowdown performance when the list of filters gets large.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)