Let's put things simpler: can SEDA+transaction encompass 2 SMX
components in a transaction ?
Thanks for the answer.
Dominique
Dominique DE VITO a écrit :
If I understand correctly, seda+transaction can't include also two
components into one transaction (like JMS-queue-reader=>WE).
Just like what you said about JCA+transaction !?
I mean, I declared :
(1) flowName="seda" + autoEnlistInTransaction="true"
(2) <jms:endpoint role="consumer" ...
connectionFactory="#jmsFactory" ...
synchronous="true"
processorName="jca"
bootstrapContext="#bootstrapContext"
resourceAdapter="#activemqRA">
with jmsFactory as "JMS Xa-enabled pooled factory"
So far, If WS BC component fails, the JMS msg is still consumed. It
looks like different than the 1st figure in
http://incubator.apache.org/servicemix/transactions.html
It seda+transaction behavior just like JCA+transaction about exchange
lifecycle (enrolment of component into the transaction) ???
Thanks.
Dominique
Guillaume Nodet wrote :
Currently, the JCA flow does not interfere with the exchange lifecycle.
I.e., it will ensure that the exchange is delivered to the target
component,
but will not rollback the transaction if the exchange is put in an ERROR
state.
But things can always be improved ;-)
On 3/21/07, Dominique DE VITO <[EMAIL PROTECTED]> wrote:
Hi,
I have defined a pipeline like this : JMS queue reader=>WS (BC).
With JCA flow (+ XA).
I test first without running tomcat providing the external WS. An error
occurs and I expect that the initial msg stays in the queue.
After starting tomcat, and re-starting SMX, no msg is found into the
JMS
queue.
Is it the normal behavior ? Or, is there something missing in my
configuration ?
Thanks.
Dominique
