servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie Goodyear (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SM-1607) JBI container should be able to initialize all SAs first and then start them
Date Tue, 02 Dec 2008 18:04:06 GMT

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

Jamie Goodyear updated SM-1607:
-------------------------------

    Attachment: sm1607.txt

See attached file 'sm1607.txt'.

This is my first 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.

The Deployment Test is updated to accommodate a verification issue that occurs with EasyMocks
during testing.

> 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
>
>
> 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.


Mime
View raw message