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-1443) After a restart the capabilities of a subsystem have changed (seem correct) before the restart they seem wrong
Date Thu, 18 Feb 2016 20:53:18 GMT

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

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

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

[ARIES-1443] After a restart the capabilities of a subsystem have changed (seem correct) before
the restart they seem wrong

This issue affects only newly installing features. The Subsystem service is registered and
added to the system repository before all of its capabilities have been computed. Because
features implicitly export everything, their capabilities must be derived from their content.
This is currently done examining constituents and filtering them based on the
Subsystem-Content header. It must be done this way for persisted subsystems, which are unaffected
by this issue.

Initially, I tried to fix the issue by looking for features in the INSTALLED state as part
of the modifiedService method of the SystemRepository because by then the consituents have
been computed and all capabilities are available. Unfortunately, this will not work for newly
installing features with apache-aries-provision-dependencies:=resolve and that remain
in the INSTALLING state.

Ultimately, the issue was fixed in BasicSubsystem by adding an additional path to both getCapabilities
and getRequirements. Newly installing subsystems can be distinguished from
persisted subsystems by the presence of a SubsystemResource, which the former will have while
the latter will not. If a SubsystemResource is present, the capabilities and
requirements can be computed from the content contained therein. This is available as the
newly installing subsystem is being added to the system repository. Persisted subsystems
continue to function as before.

Note that this should also fix ARIES-1442.

> After a restart the capabilities of a subsystem have changed (seem correct) before the
restart they seem wrong
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1443
>                 URL: https://issues.apache.org/jira/browse/ARIES-1443
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-2.0.6, subsystem-2.0.8
>         Environment: karaf pax-exam
>            Reporter: Bas
>              Labels: test-patch
>         Attachments: CapabilitiesDifferOnRestart.java.patch
>
>
> A feature subsystem should export all capabilities of its constituents and it does not
do that after a fresh install. After a restart of the subsystem core bundle it will export
all the capabilities. 
> These seems to be a difference in parsing the capabilities of a persisted subsystem and
a new subsystem.



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

Mime
View raw message