You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/03/22 12:46:43 UTC
[jira] Created: (CAMEL-1475) transactionErrorHandler should be able
to wrap routes with default policy if no policy defined
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, 1.6.1
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.
[jira] Updated: (CAMEL-1475) Easier transacted configuration of
routes
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1475:
-------------------------------
Attachment: JMS_lookup_TX_manager.patch
I was working on letting the JMS component auto lookup the TX manager as well. Patch attached.
However want to discuss it a bit more, eg what if the platform manager in Spring XML is not JMS based, eg a DataSource based = DataSourceTransactionManager. Then I assume the JMS component cannot work anyway.
And the Spring PlatformTransactionManager does not support any operations to determine if it supports your resource type (JMS, JDBC, etc.).
But it makes great sense when you have define a JTA TX manager.
But of course you just need to define the transactionManager property on the ActiveMQComponent then you are good to go anyway.
Such as:
{code:xml}
<!-- define our activemq component -->
<bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent">
<property name="connectionFactory" ref="jmsConnectionFactory"/>
<!-- define the jms consumer/producer as transacted -->
<property name="transacted" value="true"/>
<property name="transactionManager" ref="jmsTransactionManager"/>
</bean>
{code}
So what we are talking about is being able to loose the last property
<property name="transactionManager" ref="jmsTransactionManager"/>
And have Camel auto lookup the TX manager.
> Easier transacted configuration of routes
> -----------------------------------------
>
> 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
>
> Attachments: JMS_lookup_TX_manager.patch
>
>
> 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.
[jira] Commented: (CAMEL-1475) transactionErrorHandler should be
able to wrap routes with default policy if no policy defined
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51037#action_51037 ]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
Okay the {{policy}} is required to define a route as transacted. Then we do not need to configure the error handler as transactional, and thus we can just do:
{code:java}
Policy required = context.getRegistry().lookup("PROPAGATION_REQUIRED", SpringTransactionPolicy.class);
// set the required policy for this route so its transacted
from("direct:okay").policy(required).
setBody(constant("Tiger in Action")).beanRef("bookService").
setBody(constant("Elephant in Action")).beanRef("bookService");
{code}
> 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.
[jira] Commented: (CAMEL-1475) transactionErrorHandler should be
able to wrap routes with default policy if no policy defined
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51047#action_51047 ]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
Okay got this baby working now
{code:java}
from("direct:okay")
// marks this route as transacted, and we dont pass in any parameters so we
// will auto lookup and use the Policy defined in the spring XML file
.transacted()
.setBody(constant("Tiger in Action")).beanRef("bookService")
.setBody(constant("Elephant in Action")).beanRef("bookService");
{code}
And with the Spring XML below Camel will lookup beans with the type {{org.apache.camel.spi.Policy}} and if there are 1 policy defined it will use that as default.
{code:xml}
<!-- START SNIPPET: e1 -->
<!-- datasource to the database -->
<bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
<property name="driverClassName" value="org.hsqldb.jdbcDriver"/>
<property name="url" value="jdbc:hsqldb:mem:camel"/>
<property name="username" value="sa"/>
<property name="password" value=""/>
</bean>
<!-- spring transaction manager -->
<bean id="txManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
<property name="dataSource" ref="dataSource"/>
</bean>
<!-- policy for required transaction used in our Camel routes -->
<bean id="PROPAGATION_REQUIRED" class="org.apache.camel.spring.spi.SpringTransactionPolicy">
<property name="transactionManager" ref="txManager"/>
</bean>
<!-- bean for book business logic -->
<bean id="bookService" class="org.apache.camel.spring.interceptor.BookService">
<property name="dataSource" ref="dataSource"/>
</bean>
<!-- END SNIPPET: e1 -->
{code}
Next step is to make it even easier, eg to be able to lookup the PlatformManager and if there is 1 single defined use that one and use REQUIRED by default.
Then we can loose the PROPAGATION_REQUIRED bean.
> 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.
[jira] Commented: (CAMEL-1475) transactionErrorHandler should be
able to wrap routes with default policy if no policy defined
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CAMEL-1475) transactionErrorHandler should be
able to wrap routes with default policy if no policy defined
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51038#action_51038 ]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
Maybe we can add some convention over configuration so we can auto lookup the SpringTransactionPolicy
So we can shorten the route to:
{code:java}
// set the required policy for this route
from("direct:okay").policy("PROPAGATION_REQUIRED").
setBody(constant("Tiger in Action")).beanRef("bookService").
setBody(constant("Elephant in Action")).beanRef("bookService");
{code}
Maybe we can have a nicer default name for {{PROPAGATION_REQUIRED}}.
{code:java}
// set the required policy for this route
from("direct:okay").policy("REQUIRED").
setBody(constant("Tiger in Action")).beanRef("bookService").
setBody(constant("Elephant in Action")).beanRef("bookService");
{code}
Or it defaults to required if no parameters specified
{code:java}
// set the required policy for this route
from("direct:okay").policy().
setBody(constant("Tiger in Action")).beanRef("bookService").
setBody(constant("Elephant in Action")).beanRef("bookService");
{code}
And while we are at it, maybe the *policy* itself could be renamed to something that better reflects its a transaction
{code:java}
// this route is transacted
from("direct:okay").transacted().
setBody(constant("Tiger in Action")).beanRef("bookService").
setBody(constant("Elephant in Action")).beanRef("bookService");
{code}
> 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.
[jira] Commented: (CAMEL-1475) transactionErrorHandler should be
able to wrap routes with default policy if no policy defined
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51045#action_51045 ]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
Improved the configuration as the TransactedErrorHandlerBuilder is not needed to be configured.
trunk: 762267
> 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.
[jira] Updated: (CAMEL-1475) transactionErrorHandler should be able
to wrap routes with default policy if no policy defined
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1475:
-------------------------------
Fix Version/s: (was: 1.6.1)
> 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.
[jira] Commented: (CAMEL-1475) transactionErrorHandler should be
able to wrap routes with default policy if no policy defined
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51077#action_51077 ]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
New Revision: 762641
Introduced transacted DSL keyword to more clearly state a route is transacted. Also Camel can autolookup the spring transaction policy, hence to make the Spring XML configuration a bit 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.
[jira] Updated: (CAMEL-1475) Easier transacted configuration of
routes
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1475:
-------------------------------
Summary: Easier transacted configuration of routes (was: transactionErrorHandler should be able to wrap routes with default policy if no policy defined)
> Easier transacted configuration of routes
> -----------------------------------------
>
> 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.
[jira] Commented: (CAMEL-1475) transactionErrorHandler should be
able to wrap routes with default policy if no policy defined
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51041#action_51041 ]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
See discussion at
http://www.nabble.com/-DISCUSS----Camel-2.0---Easier-Camel-Spring-Transaction-configuration-td22904091.html
> 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.
[jira] Commented: (CAMEL-1475) Easier transacted configuration of
routes
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51079#action_51079 ]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
TODO: Update wiki page
> Easier transacted configuration of routes
> -----------------------------------------
>
> 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.
[jira] Work started: (CAMEL-1475) transactionErrorHandler should be
able to wrap routes with default policy if no policy defined
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on CAMEL-1475 started by Claus Ibsen.
> 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.
[jira] Commented: (CAMEL-1475) Easier transacted configuration of
routes
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51172#action_51172 ]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
Camel can now auto lookup the PlatformTransactionManager so the PROPAGATION_REQUIRED spring bean is not needed anymore, if you want to use the default settings.
trunk: 764683
> Easier transacted configuration of routes
> -----------------------------------------
>
> 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.
[jira] Commented: (CAMEL-1475) Easier transacted configuration of
routes
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51078#action_51078 ]
Claus Ibsen commented on CAMEL-1475:
------------------------------------
And now Spring DSL is also easier
trunk: 762645.
> Easier transacted configuration of routes
> -----------------------------------------
>
> 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.
[jira] Resolved: (CAMEL-1475) Easier transacted configuration of
routes
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-1475.
--------------------------------
Resolution: Fixed
Keeping the JMS component as is.
Last piece off code committed: 765920
> Easier transacted configuration of routes
> -----------------------------------------
>
> 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
>
> Attachments: JMS_lookup_TX_manager.patch
>
>
> 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.
[jira] Issue Comment Edited: (CAMEL-1475) Easier transacted
configuration of routes
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51079#action_51079 ]
Claus Ibsen edited comment on CAMEL-1475 at 4/14/09 1:05 AM:
-------------------------------------------------------------
Update wiki page *DONE*
was (Author: davsclaus):
TODO: Update wiki page
> Easier transacted configuration of routes
> -----------------------------------------
>
> 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
>
> Attachments: JMS_lookup_TX_manager.patch
>
>
> 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.