camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-372) JMS endpoints should default to be transactional; using the JMS transaction manager if no transaction manager is explicitly configured?
Date Mon, 18 May 2009 14:25:50 GMT

     [ 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.


Mime
View raw message