[
https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51025#action_51025
]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
I am thinking that we should have a discussion on this matter how to let the TX
configuration be easier in Camel
The codebase requires the {{policy}} to be defined in the route to properly
configure a route as transacted.
This is in fact fine as it explicit declare the route as transacted.
However policy is a generic term, so we could consider renaming it to transacted
Then the error handler configuration could probably be optional as if its
missing the transacted could auto create one on demand, such as looking for a
TX manager in the registry or how we can make it easier.
> transactionErrorHandler should be able to wrap routes with default policy if
> no policy defined
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-1475
> URL: https://issues.apache.org/activemq/browse/CAMEL-1475
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core, camel-spring
> Affects Versions: 1.6.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> See TransactionalClientWithRollbackTest in camel-spring
> The {{.policy(required)}} is needed in the routes even though we have a
> global transaction error handler with a default policy set:
> {code}
> errorHandler(transactionErrorHandler(required));
> {code}
> So Camel should fallback and use the global policy if the route itself does
> not have a policy defined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
