aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sameer Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARIES-1894) Provide Require capability not working for Composite Subsystem
Date Fri, 15 Feb 2019 10:51:00 GMT

     [ https://issues.apache.org/jira/browse/ARIES-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sameer Gupta updated ARIES-1894:
--------------------------------
    Priority: Critical  (was: Major)

> Provide Require capability not working for Composite Subsystem
> --------------------------------------------------------------
>
>                 Key: ARIES-1894
>                 URL: https://issues.apache.org/jira/browse/ARIES-1894
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>            Reporter: Sameer Gupta
>            Priority: Critical
>         Attachments: messagedisplay.esa, msgdispconsumer.jar
>
>
> 1 - I have a composite subsystem  "messagedisplay.esa" which has a bundle with a provide

> capability, the provide capability is mentioned in both the bundle manifest 
> which is inside the bundle manifest and the subsystem manifest as well.
> 2. I have a stand alone bundle "msgdispconsumer" which requires this capability and mentions
this in standalone bundle manifest.mf file
> In case of system migrations, if the Bundle gets deployed before the ESA 
> subsystem, the bundle does not start as expected and has to be manually 
> started once the provide capability is deployed.
> However, if I mark the subsystem as feature, then, as soon as the subsystem 
> is deployed, the standalone bundle also goes to active state, thus removing 
> need for manual intervention.
> Provide Require capability does not seem to have the same effect for Composite Subsystem
as it has for feature subsystem.
> Test Case 1: Deploy the Composite Subsystem i.e the attached messagedisplay.esa file
and then start it and then deploy the msgdispconsumer bundle, the bundle auto-wires and starts.
> Test Case 2: Deploy the msgdispconsumer bundle, try and start it, it fails stating a
required capability is missing, deploy the subsystem i.e. the messagedisplay.esa file now,
the Subsystem installs but does not auto wire the bundle msgdispconsumer  is still in installed
state, start the msgdispconsumer bundle, it starts and does not throw the capability missing
error.
> Test Case 3: Open the .ESA file in winrar like tool, change the subsytem type from Subsystem-Type:
"osgi.subsystem.composite" to "osgi.subsystem.feature".
> Exit the karaf console and restart to clear the cache.
> Deploy the msgdispconsumer bundle, try and start it, it fails stating a required capability
is missing, deploy the subsystem i.e. the messagedisplay.esa file now, the consumer bundle
msgdispconsumer also starts automatically even when the ESA subsytem is only in installed
state. 
> Why does behavior in Test case 3 not work for test case 2 scenario, i.e. autowiring happens
for feature subsystem  but  not for composite subsystem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message