Redefining the Transaction model for Sandesha2
----------------------------------------------
Key: SANDESHA2-106
URL: https://issues.apache.org/jira/browse/SANDESHA2-106
Project: Sandesha2
Issue Type: Improvement
Reporter: Chamikara Jayalath
In the Hackathon we decided to redefine the transaction model to suite more
practical scenarios. I'll post some of the things we discussed. Need more
comments and ideas from the user/dev community.
A Sandesha2 transaction may be scoped to the Sandesha2 system or it may be
bound to a real user transaction. There can be two points where Sandesha2 can
be bound to a user transaction.
1. In the client side stuff done at the SandeshaOutHandler can be bound to the
transaction of the application client.
2. In the server side the Sandesha2 transaction of the InvokerWorker may be
bound with a server side application level transaction.
We can add a method storageManager.isUserTransactionInScope(messageContext) to
see weather a particular message is bound with a user level transaction.
Depending on this Sandesha2 may behave differently.
It is great if somebody who was at the Hackathon can post a image of the
drawing we came up with.
--
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]
