[ https://issues.jboss.org/browse/JBTM-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095050#comment-13095050 ]
Tom Jenkinson commented on JBTM-1820:
-------------------------------------
We need to create our own quickstart for this.
We could use WildFly-camel: https://github.com/wildfly-extras/wildfly-camel but probably would be easier to just use a main and spring. Maybe sequence it after JBTM-855 if you want to go spring route.
> Integrate with Camel to support XA Transaction
> ----------------------------------------------
>> Key: JBTM-1820
> URL: https://issues.jboss.org/browse/JBTM-1820> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Application Server Integration
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 6.later
>>> From Ning Jiang (njiang at redhat.com)
> {noformat}
> Camel is using Spring TransactionTemplates to implement the Transactional Client pattern[1].
> As the Spring PlatformTransactionManager cannot manage the multiple resources, we are using the atomikos to show the user how to manage the transactions between JMS and DB resource. It could great if we can replace the atomikos with narayana, then we can promote this example as reference to SA who can sale the solution to the customer.
> Another interesting task could be using the narayana JTA wrapper classes to replace the Spring TransactionTemplate in Camel. As we don't want to build out products on top of Spring framework, using narayana could help us to get ride of Spring and introduce the narayana to integration customer.
> [1]http://camel.apache.org/transactional-client.html> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)