I don't specifically have one in mind.
In exploring Camel I found that one can perform the basic messaging
functions in Java using Camel API's only but got messy with transactions.
My preference would be for Camel to expose a JTA. If that transparently
invoked Spring TX that would be fine - analogous to the various
components wrapping Spring but not exposing it directly in Java.
What other options exist outside a container (or inside) for transaction
support that would work with Camel?
Thank you for responding,
Colin
Claus Ibsen wrote:
On Mon, Mar 23, 2009 at 5:06 PM, Colin Ruthven <ruth...@attglobal.net> wrote:
Is it possible to use transactions in Camel messaging (eg JMS) without
Spring intruding? Camel may use Spring underneath the covers but I don't
want to use it inside my application.
Or at least only use Camel API's to do this or be able to plug other
solutions in.
Hi
camel-jms uses spring-jms under the covers. And the TX support we have
in Camel relies on Spring TX as well.
But you can disable the error handler completely in Camel and let
whatever external system you use handle the TX.
In java DSL:
errorHandler(noErrorHandler));
In Spring DSL its something like this (I sit with laptop in hand and
dont have code editor open)
<bean id="myNoErrorHandler"
class="org.apache.camel.builder.NoErrorHandlerBuilder"/>
<camel errorHandlerRef="myNoErrorHandler" ...>
</camel>
The documentation seems to go both ways, suggesting that Spring is the
"default" but in other places it looks like that's the only approach
available.
Usually Spring TX is very flexible, so you can wire it up to integrate
with your external system for the TX management.
What kind of other framework/system do you want to handle the TX?
Any comments appreciated.
Thanks,
Colin
