DAS should not commit individual commands as part of applyChanges
-----------------------------------------------------------------
Key: TUSCANY-1087
URL: https://issues.apache.org/jira/browse/TUSCANY-1087
Project: Tuscany
Issue Type: Bug
Components: Java DAS RDB
Affects Versions: Java-DAS-Mx
Reporter: Kevin Williams
Fix For: Java-DAS-Mx
The DAS must commit all commands resulting from ChangeSummary processing as an
atomic unit.
Sam Su's original note:
"Hi kevin, thanks for you response.
I debuged the application in Eclipse, I was sure that after user1 was
inserted into database without an exception, a commit was performed on the
connection.
as two data objects needed to be inserted into database in my program, from
the DAS source code, DAS will produce two different InsertCommandImpl
instances for these two changes.The 'success' flag is in two different
command instance, furthermore, it's a method scope variable, it can not be
shared between two command instances. When command instance for user1
execute without an exception, it will proceed to perform a commit on the
connection, command instance for user2 execute will throw an exception, so
rollback. However the use1 has been already commited to database although
use2 fail to be inserted into database."
I have added a test "TransactionTests.estReadModifyApply()" t hat demonstrates
this defect.
--
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]
