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/09/28 11:11:50 UTC
[jira] Updated: (TUSCANY-1816) local container managed transaction
support test case
[ https://issues.apache.org/jira/browse/TUSCANY-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gengshaoguang updated TUSCANY-1816:
-----------------------------------
Attachment: transaction.zip
This zip is the folder I worked in Tuscany-1.0-RC3/modules, but is will not run untill my suggested changes applied to implementation-java-runtime model.
The diff of implementation-java-runtime is in the README
> local container managed transaction support test case
> ------------------------------------------------------
>
> Key: TUSCANY-1816
> URL: https://issues.apache.org/jira/browse/TUSCANY-1816
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-Next
> Environment: jdk1.6 win2000 svn trunk derby
> Reporter: gengshaoguang
> Attachments: transaction.zip
>
>
> Hello Tuscany Funs,
> I attach this folder of files to demonstrate scenarios of a container managed local transaction support, my implementation is very common to those popular CMPs, and its very low level too, and component could use a java.sql.Connection provided by TransactionInfo which is held for each user thread..
> TODOs:
> I don't know what is the best way to describe out a transaction need for a component, but Annotations would be easier for me.
--
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