[
https://issues.apache.org/activemq/browse/SM-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jamie Goodyear updated SM-1607:
-------------------------------
Attachment: sm1607b.txt
See attached file 'sm1607b.txt'.
This is my second attempt at resolving this issue, so please review before
trying this one out.
The basics of this patch includes having the Deployment Service start method
internally initializes all SAs. To facilitate this the Service Assembly Life
Cycle is updated to include an init method that handles initializing the
assembly's SUs.
I've included updates to handle the two issues Guillaume noted. I now suspend
the broker before initializing any SAs, secondly I have modified the restore
call to specify if a forceInit is required for SUs (the original behavior is
maintained by restore() signature).
No modifications are required to the DeploymentTests using this patch.
> 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
> 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.
