[
https://issues.apache.org/jira/browse/ARIES-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Ross updated ARIES-1021:
-----------------------------
Fix Version/s: subsystem-core-1.0.0
> Implementation of AriesSubsystem.addRequirements must not assume the region
> only has edges to the parent subsystem's region.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: ARIES-1021
> URL: https://issues.apache.org/jira/browse/ARIES-1021
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Reporter: John Ross
> Assignee: John Ross
> Fix For: subsystem-core-1.0.0
>
>
> The addRequirements method on the AriesSubsystem interface allows clients to
> add additional requirements (i.e. those beyond what was in the deployment
> manifest) to a subsystem. Effectively, this means any capability matching a
> specified requirement will be allowed into the subsystem's region from the
> parent region.
> However, the implementation assumes that all edges of the current region
> point to the parent, which is not the case. For example, currently there is
> always at least one edge that does not fit that pattern, namely the edge that
> allows subsystem services to be seen from the root region. Other edges might
> also exist if region digraph was manipulated outside of the subsystems API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
