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
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
