[
https://issues.apache.org/activemq/browse/CAMEL-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48302#action_48302
]
James Strachan commented on CAMEL-372:
--------------------------------------
We still haven't figured out why reusing a transaction manager is bad - it
should work across many threads & transactions.
FWIW setting the JMS endpoint to transactional by default only applies to
InOnly. i.e. oneway JMS operations (which is the common use case).
For InOut we should not enable transacted by default - since its typically not
what users want/expect.
> 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.
