Yup, right. The choices are to either wrap the XAResource to behave as a Participant, or wrap the JTA Transaction to behave as a Participant. Since there are lots of XAResources but only one transaction, we prefer to do the latter. The bridge creates the JTA Transaction (actually a subtransaction in effect) for you and enlists it when needed, that is its job.
wow, thanks for your fast respone. So I apologize in advance for what might be a stupid question that has allready been asked and answered.
I have had a look at the JaxWSTransactionBridgeHandler.java from the bridging example, so do I assume correctly that a Web Service which uses bridging to wrapp a JTA transaction, has to use the JTA transactionManager to enlist the XAResource to the jta transaction? So this leads to my next question, does the XTS use a speciall transactionManager or does it use the JTA transactionManager and though bridging is used in the first place anyways?
thanks so much
Enlistment of resources into the JTA transaction can be done directly by your application. but would more usually be done indirectly by the application server. For example, you may access an EJB that is backed by a database, the app server will take case of enlisting the underlying db connection's XAResource into the tx.
The transaction engine for XTS shares some common code with the JTA transaction manager, but that is just an implementation detail. From a perspective of the system design they are independent.
Ok I think I got it, thanks so much for your help