[jira] Resolved: (SM-1607) JBI container should be able to initialize all SAs first and then start them

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

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

Guillaume Nodet resolved SM-1607.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 3.3.1
         Assignee: Guillaume Nodet

Sending        servicemix-core/src/main/java/org/apache/servicemix/jbi/framework/DeploymentService.java
Sending        servicemix-core/src/main/java/org/apache/servicemix/jbi/framework/ServiceAssemblyLifeCycle.java
Transmitting file data ..
Committed revision 725284.

Thanks a lot Jamie for this patch.

I haven't backported this fix to 3.2 branch because it does not make any sense.
This fix is related to the change in the endpoint lifefycle that occured in all components for 3.3, so in 3.2, endpoints are activated while SUs are started.
Therefore, the behavior would not be changed in 3.2.

> JBI container should be able to initialize all SAs first and then start them
> ----------------------------------------------------------------------------
>
>                 Key: SM-1607
>                 URL: https://issues.apache.org/activemq/browse/SM-1607
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-core
>    Affects Versions: 3.2.2
>            Reporter: Ron Gavlin
>            Assignee: Guillaume Nodet
>             Fix For: 3.3.1
>
>         Attachments: sm1607.txt, sm1607b.txt
>
>
> This issue is related to issue SM-1554

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.