aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1538) Never fail a subsystem resolution because an already resolved resource has a missing dependency.
Date Mon, 25 Apr 2016 13:00:14 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256300#comment-15256300
] 

ASF subversion and git services commented on ARIES-1538:
--------------------------------------------------------

Commit 1740835 from [~jwross@us.ibm.com] in branch 'aries/trunk'
[ https://svn.apache.org/r1740835 ]

[ARIES-1538] Never fail a subsystem resolution because an already resolved resource has a
missing dependency.

When no matching capabilities are found, if the requirement is not optional and the requirement
resource is already resolved, have the resolve context add a missing capability. Do not fail
the
subsystem resolution.

> Never fail a subsystem resolution because an already resolved resource has a missing
dependency.
> ------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1538
>                 URL: https://issues.apache.org/jira/browse/ARIES-1538
>             Project: Aries
>          Issue Type: Improvement
>          Components: Subsystem
>    Affects Versions: subsystem-2.0.8
>            Reporter: John Ross
>            Assignee: John Ross
>
> The implementation should be forgiving and never fail the resolution of a subsystem when
one of its dependencies is an already resolved resource with a missing dependency. This scenario
can occur now due to the change made as part of ARIES-1445 whereby an empty wiring map is
always returned by the resolve context to the resolver in order to detect indirect dependencies
and maintain an accurate use count. Also, note that the scenario can only occur with resources
installed outside of the subsystem framework. We suspect that, by far, the most common occurrence
will be related to non-subsystem resources having effective:=active requirements.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message