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/05/18 16:25:50 UTC
[jira] Resolved: (CAMEL-372) JMS endpoints should default to be
transactional; using the JMS transaction manager if no transaction manager
is explicitly configured?
[ https://issues.apache.org/activemq/browse/CAMEL-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-372.
-------------------------------
Resolution: Won't Fix
Lets leave it as is.
The end user must set *transacted=true* to use JMS transactions. This is the best behavior as no other components like JDBC default to be transacted.
> JMS endpoints should default to be transactional; using the JMS transaction manager if no transaction manager is explicitly configured?
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-372
> URL: https://issues.apache.org/activemq/browse/CAMEL-372
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Assignee: Willem Jiang
> Fix For: 2.0.0
>
>
> Its such a common use case - using camel-jms should be transactional out of the box unless the user explicitly disables transactions. So defaulting the transactionManager property seems to make sense
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.