David Bosschaert created ARIES-1152:
---------------------------------------
Summary: Lifecycle issue with subsystem that is a transitive
dependency
Key: ARIES-1152
URL: https://issues.apache.org/jira/browse/ARIES-1152
Project: Aries
Issue Type: Bug
Components: Subsystem
Reporter: David Bosschaert
This bug relates to lifecycle issues experienced with subsystems that are a
transitive dependency of another subsystem.
I have a subsystem installed that has a dependency on another subsystem. The
dependency is obtained via a Repository service.
(Note I use some simple subsystem gogo commands to illustrate the issue)
{code}subsystem:list
0 ACTIVE org.osgi.service.subsystem.root 1.0.0
1 ACTIVE jbosgi-repository 2.0.1
2 RESOLVED subsystemA 0.0.1
3 RESOLVED subsystemB 0.5.0{code}
Subsystem 3 is a dependency of subsystem 2, so when uninstalling 2, subsystem 3
gets automatically uninstalled too:
{code}g! subsystem:uninstall 2
g! subsystem:list
0 ACTIVE org.osgi.service.subsystem.root 1.0.0
1 ACTIVE jbosgi-repository 2.0.1{code}
So far so good...
However, when I install another subsystem that, again, has a dependency on
subsystemB, the system gets confused:
{code}g! subsystem:install .../subsystemC.esa
g! subsystem:list
0 ACTIVE org.osgi.service.subsystem.root 1.0.0
1 ACTIVE jbosgi-repository 2.0.1
3 UNINSTALLED subsystemB 0.5.0
4 INSTALLED subsystemC 0.0.1{code}
The subsystem service for subsystemB appears again, but in the uninstalled
state.
Trying to start the new subsystem gives an error:
{code}g! subsystem:start 4
gogo: SubsystemException: Cannot stop from state UNINSTALLED{code}
And my subsystemC is now in the RESOLVED state, which is not really correct
since its dependency in subsystemB has been UNINSTALLED:
{code}g! subsystem:list
0 ACTIVE org.osgi.service.subsystem.root 1.0.0
1 ACTIVE jbosgi-repository 2.0.1
3 UNINSTALLED cdi-subsystem 0.5.0
4 RESOLVED devicemon-decl 0.0.1{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
