Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.215.45 as permitted sender)
Received-SPF: pass (google.com: domain of claus.ibsen@gmail.com designates
 10.112.23.39 as permitted sender) client-ip=10.112.23.39;
MIME-Version: 1.0
In-Reply-To: <1330783849034-5533706.post@n5.nabble.com>
References: <1330538975066-5525681.post@n5.nabble.com>
 <4101792725898597996@unknownmsgid>
 <1330783849034-5533706.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sat, 3 Mar 2012 16:34:25 +0100
Message-ID: 
 <CAGB5yNncvGcDPrp+oYchsUvwN1nioTrFUKFcoAjkE_FCkwdCVg@mail.gmail.com>
Subject: Re: Camel features and falling-back to Camel components
To: dev@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Sat, Mar 3, 2012 at 3:10 PM, E.Gherardini <e.gherardini@hotmail.com> wrote:
> Hello Raul and thanks for replying!
>
> I am concerned about transactional camel plugs I need to hook up in my
> component indeed.
>
> I am aware about the async routing engine, but I do not know how to "join"
> camel transactions from my component, or, to better say: what should the
> component to allow camel control it in a transactional way ?
>

Its Spring Transaction manager which orchestrates the transaction. So
look into how you can enlist your resource
into a Spring TX manager.

The <transacted> just ensure the that the processing of the message
occurs in a Spring managed transacted (eg using a transaction
template, and issue the work in a doInTransaction method). As well as
the routing engine will run in synchronous mode due Spring TX manager
need to run in the same TX to work properly.

See this source for details
https://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/main/java/org/apache/camel/spring/spi/TransactionErrorHandler.java


> Thanks a lot,
> Emanuele
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-features-and-falling-back-to-Camel-components-tp5525681p5533706.html
> Sent from the Camel Development mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/