Service Unit Activation Sequence

[objectorange <br...@briantaylor.us>]

Given the following scenario: 

ServiceMix (SMX) 3.3.1 contains in its hotdeploy a CXF BC JMS service unit
(binding) and a CXF SE service unit (a 'data' service). While up and
running, SMX receives XML messages to a queue through its JMS binding
routing those to the 'data' service. If SMX is shutdown, XML messages begin
to queue up. When SMX is restarted, it activates the JMS binding prior to
the 'data' service causing the NMR to complain 'service not registered' and
in a split second later registers the 'data' service. Is there a way to
prevent or handle this effectively? 

Thanks in advance, 
Brian 

--
View this message in context: http://servicemix.396122.n5.nabble.com/Service-Unit-Activation-Sequence-tp4492187p4492187.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Service Unit Activation Sequence

[Freeman-2 <fr...@gmail.com>]

Hi,

If you package those two SU in same SA, then the sequence of SU start is the
sequence that SU dependency in the SA's pom.xml, that said, you just need
put CXF SE su dependency before CXF BC JMS su in the SA's pom.xml.

(P.S. Sorry for the late reply - we've had a bit of trouble receiving
mails that were posted to Nabble instead of directly to the mailing
lists so your original mail kind of dropped off the radar for us)

Freeman

--
View this message in context: http://servicemix.396122.n5.nabble.com/Service-Unit-Activation-Sequence-tp4492187p4534901.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.