| Guido Anzuoni (JIRA) 2006-12-22, 7:11 am |
| [ http://issues.apache.org/jira/brows...action_12460433 ]
Guido Anzuoni commented on JDO-445:
-----------------------------------
The simple approach would be no transaction no PM.
If we would try a more sophisticated approach, try to consider the scenario where
you begin with a ordinary PM and then you begin a global transaction.
Suppose you get a PM without a global transaction and begin to modify some objetcs and flush.
At his point (considering for simplicity a RDBMS backend) the PM should have started
a local transaction on the DataSource Connection acquired.
Now you begin a global transaction.
What to do now ?
In this case you could not "join" the global transaction but you should complete the local one.
But, what happen to the DataSource Connection itself used to operate until now ?
Its corresponding XAResource is enlisted ?
Is still possible to commit() the local transaction on the Connection ?
For the second point, I would say that is sufficient to have a TransactionManager, that can be
setup even in a J2SE environment
> Add convenience method that returns a PersistenceManager proxy
> --------------------------------------------------------------
>
> Key: JDO-445
> URL: http://issues.apache.org/jira/browse/JDO-445
> Project: JDO
> Issue Type: New Feature
> Components: api2, api2-legacy
> Reporter: Michelle Caisse
> Assigned To: Craig Russell
> Fix For: JDO 2 maintenance release 1
>
> Attachments: PMProxy-patch.txt
>
>
> In Chapter 8, add a convenience method that returns a PersistenceManager proxy that can be used in web and ejb containers to dynamically bind to the transaction-associated PersistenceManager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|