aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (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 Wed, 17 Feb 2016 20:17:18 GMT

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

John Ross commented on ARIES-1443:
----------------------------------

When first being installed, the feature's Subsystem service is registered before its constituents
have been computed. The registration leads to a call to SystemRepository.addingService where
the only existing capability is osgi.identity.

After a restart, the constituents have already been computed so all capabilities are returned
to the SystemRepository as part of the registration.

> 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