camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <r...@evosent.com>
Subject Re: Two routes, two transactions
Date Thu, 04 Oct 2012 09:39:39 GMT
To be honest, I don't understand why you want Camel to take care of the
transactions if all business logic is buried inside beans and the FTP
consumer is not transactional either. It seems like you don't need
transactions to be shared across beans either.

May I ask what behaviour exactly you are trying to achieve? Are you trying
to keep the file on the FTP server if something fails?

P.S.: Shifting conversation to users mailing list. On next reply, please
remove the dev@ mailing list from the recipient list.

Regards,

*Raúl Kripalani*
Apache Camel Committer
Enterprise Architect, Program Manager, Open Source Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk <http://twitter.com/raulvk>

On Wed, Oct 3, 2012 at 6:03 PM, lolo <Laurent.Gaertner@lchclearnet.com>wrote:

> This is the configuration I'm using:
> <http://camel.465427.n5.nabble.com/file/n5720505/forum.jpg>
>
> But I'm still having the same problem
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Two-routes-two-transactions-tp5720484p5720505.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message