[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-119) Blueprint Container service is unregistered
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Thu Oct 8 05:24:06 EDT 2009
[ https://jira.jboss.org/jira/browse/JBOSGI-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler updated JBOSGI-119:
----------------------------------
Fix Version/s: JBossOSGi 1.0.x
(was: JBossOSGi 1.0.0 Beta4)
> Blueprint Container service is unregistered
> -------------------------------------------
>
> Key: JBOSGI-119
> URL: https://jira.jboss.org/jira/browse/JBOSGI-119
> Project: JBoss OSGi
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jboss-osgi-blueprint
> Reporter: Thomas Diesler
> Fix For: JBossOSGi 1.0.x
>
>
> When the Blueprint Container must be destroyed because: the Blueprint
> bundle has stopped, there is a failure, or the Blueprint extender is stopped,
> then the Blueprint Container service is unregistered and all managers are
> deactivated. This will unregister any services and disable listeners, which
> release the component instances. Then all component instances are
> destroyed in reverse dependency order. That is, a component instance is
> destroyed when no other component instances depend on it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-osgi-issues
mailing list