You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "gengshaoguang (JIRA)" <tu...@ws.apache.org> on 2007/10/26 04:50:50 UTC
[jira] Updated: (TUSCANY-1869) one step further, enlist *ws over
jms* and local XAResource in one transaction
[ https://issues.apache.org/jira/browse/TUSCANY-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gengshaoguang updated TUSCANY-1869:
-----------------------------------
Attachment: sca_diagram_2_references_in_1_transaction.gif
Hi every one:
This diagram shows that a further intention to enlist XAResources into one transaction.
Here are a local component which operate on any XAResources and another reference of a remote service.
Any failure of the two will cause both rollback.
But one problem is: JCA under a transaction will cause the message not reach the endpoint until the transaction commit. This is much different from a database transaction which could be leveraged be isolation.
> 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: 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org