Thanks for bringing this up. I have reported this internally so the documentation can be fixed.
Yes XA is supported and it is the Geronimo manager which is being shipped by default, eg its the exact same manager.
So I can utilize XA transactions in all parts of Fuse ESB, including Camel?
You can use XA with the resources which supports XA such as AMQ, most JDBC drivers etc. Usually you setup and configure this in XML files, like you would do with the Spring Framework.
There is a excerpt from chapter 9 from the Camel in Action book which shows that:
The full chapter is only available in the book available at Amazon, Manning etc.
There are other TX guides here
Documentation (http://fusesource.com/docs/esb/4.3.1/esb_deploy_osgi/ESBOSGiIntro-Txn.html) states:
"In order to enlist multiple resources in the same transaction (where a transaction is committed through the 2-phase commit protocol), it is necessary for each participating resource to provide an XA switch. An XA switch is an object that enables the transaction manager to control a resource manager through the XA interface, javax.transaction.xa.XAResource.
How to enlist additional resources in JTA transaction (manager by Fuse ESB) for Camel route?
Is there any example of using 2 resources in JTA transaction?
E.g. first - JMS (that already participate in transaction thanks to in configuration in Fuse ESB) and other - some external DB. How to add DB data source to JTA transaction if DB ds supports XA transactions?
It's usual case.
There is no one know how to organize real multi-resource transaction in Fuse ESB? Or that kind of support for subscribed users only ?
Is there any production deployments of Fuse ESB that uses it JTA capabilities?