Hi

Background is CAMEL-1475, however the ticket title is a bit misleading

This morning I got Camel to be able to use transacted routes without
you have to remember to configure a transactedErrorHandler.
This makes it a bit easier to use transacted routes in Camel.

So what you must do is use the *policy* DSL to define that this route
is transacted.
It still requires all the spring XML gobble to setup the TX manager
and all that verbose XML you cannot remember.
We can look at improving this later, want to keep the two of them
separated to not loose oversight.

What I wants to discuss is that I think the *policy* DSL keyword is a
bit too loose. I would like it to be renamed to something that states
its transacted, eg
a) transacted
b) transaction
c) transactedPolicy
d) transactionPolicy

As the JMS component have a special *transacted* URI option, I would
like the DSL to use same name as well.
So I am in favor of option A.

CAMEL-1475 also hints some more improvements we can do with convention
over configuration, eg if there is only one SpringTransactionPolicy in
the XML then use that.



-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration

Reply via email to