[
https://issues.apache.org/jira/browse/TUSCANY-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gengshaoguang updated TUSCANY-1869:
-----------------------------------
Attachment: derby_jdbc_XAResource.png
Diagram derby* shows the XAResource provided by derby.
So a derby manipulate component (such as an implementation-das) will be
enlisted in a global transaction manager only if it use Objects in this diagarm.
(diagram mysql* has a mistake: XAResource is under package javax.tranaction.xa)
Furtherly, an factory like the one from objectweb's xapool could be developed
to flatten the differences of using XAResource of different database vendors.
> one step further, enlist *ws over jms* and local XAResource in one transaction
> ------------------------------------------------------------------------------
>
> Key: TUSCANY-1869
> URL: https://issues.apache.org/jira/browse/TUSCANY-1869
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-Next
> Environment: svn trunk, jencks, activemq
> Reporter: gengshaoguang
> Attachments: derby_jdbc_XAResource.png, mysql_jdbc_xaresource.png,
> outbound_xaresource.png, sca_diagram_2_references_in_1_transaction.gif
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
