You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2013/01/18 09:30:13 UTC

[jira] [Updated] (ARIES-1004) When the framework is being shut down, blueprint bundles are not shut down orderly

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

Guillaume Nodet updated ARIES-1004:
-----------------------------------

    Fix Version/s: blueprint-core-1.0.2
         Assignee: Guillaume Nodet
      Description: The reason is that the extender can be at a lower start level and is shut down after other blueprint bundles.  The extender needs to intercept the STOPPING event for the system bundle and stop all bundles in the correct order.
          Summary: When the framework is being shut down, blueprint bundles are not shut down orderly  (was: When the framework is )
    
> When the framework is being shut down, blueprint bundles are not shut down orderly
> ----------------------------------------------------------------------------------
>
>                 Key: ARIES-1004
>                 URL: https://issues.apache.org/jira/browse/ARIES-1004
>             Project: Aries
>          Issue Type: Bug
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: blueprint-core-1.0.2
>
>
> The reason is that the extender can be at a lower start level and is shut down after other blueprint bundles.  The extender needs to intercept the STOPPING event for the system bundle and stop all bundles in the correct order.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira