You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Samuel Bratton (JIRA)" <ji...@apache.org> on 2015/08/05 21:31:06 UTC
[jira] [Updated] (ARIES-1348) subsystems that are dependencies are
not auto started
[ https://issues.apache.org/jira/browse/ARIES-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samuel Bratton updated ARIES-1348:
----------------------------------
Attachment: ARIES-1348.patch
The installed dependencies were not being resolved. Change code to resolve dependencies during start
> subsystems that are dependencies are not auto started
> -----------------------------------------------------
>
> Key: ARIES-1348
> URL: https://issues.apache.org/jira/browse/ARIES-1348
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Affects Versions: subsystem-2.0.2
> Environment: all
> Reporter: Samuel Bratton
> Attachments: ARIES-1348.patch
>
>
> Auto start does not work in the following scenario:
> - bundle a in Feature a (Fa) imports package x
> - composite b (Cb) exports package x from content bundle b
>
> 1) install Cb, install Fa, start Fa
> start fails with framework resolution error on bundle importing x
> but
> 2) install Cb, start Cb, install Fa, start Fa
> the start works.
> In case 1) Cb should have it active count incremented and be started automatically per OSGI.cmpn-6.0.0 134.12.2 Active Use Count.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)