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

Thomas Watson commented on ARIES-1465:
--------------------------------------

This is a known issue that I think we even mention in the specification.  See 
section 134.18:

<spec>
When the Subsystems implementation is stopped all of the installed Subsystems 
must be persistently
stored and present when the Subsystems implementation becomes active again. 
This includes
any bundles that got installed as part of a Subsystem installation. The 
Subsystems implementation
is not required to do any additional cleanup when the Subsystems implementation 
is stopped
or uninstalled. All bundles that got installed as a result of installing a 
Subsystem may still be installed
after stopping or uninstalling the Subsystems implementation bundle. If it is 
important to
clean up the bundles associated with a Subsystem installation then the 
Subsystem should be uninstalled
before uninstalling the Subsystems implementation.
</spec>

The issue is that a bundle cannot detect that it is being uninstalled so there 
is no way for the impl to tell it is being uninstalled.  It would require a 
separate 'helper' bundle to be installed that listens for when the subsystem's 
impl is uninstalled.


> Stopping the Subsystem-Core bundle does not remove synthesized bundles
> ----------------------------------------------------------------------
>
>                 Key: ARIES-1465
>                 URL: https://issues.apache.org/jira/browse/ARIES-1465
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-2.0.8
>            Reporter: David Bosschaert
>
> The Aries Subsystems implementation generates synthesized bundles, such as:
> {code}org.osgi.service.subsystem.region.context.0{code}
> However, when the Aries Subsystem implementation is stopped/uninstalled these 
> generated bundles should disappear. This is currently not happening.



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

Reply via email to