[
https://issues.apache.org/activemq/browse/CAMEL-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51274#action_51274
]
Claus Ibsen edited comment on CAMEL-372 at 4/19/09 12:25 AM:
-------------------------------------------------------------
Willem
Yeah I have been trying to change the defaults and I think the issue with
{{from (jms) -> to (jms)}} with *inOut* in the same route will fireback end
users.
So we can keep the option as disabled by default.
Even though it would be unusual to use JMS *without* transaction in a real
system.
Any thoughts from others?
was (Author: davsclaus):
Willem
Yeah I have been trying to change the defaults and I think the issue with
{{from (jms) -> to (jms)}} with *inOut* in the same route will fireback end
users.
> 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.
