db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-445) Add convenience method that returns a PersistenceManager proxy
Date Sat, 23 Dec 2006 00:59:21 GMT
    [ http://issues.apache.org/jira/browse/JDO-445?page=comments#action_12460627 ] 
Craig Russell commented on JDO-445:

These comments were made during the JDO TCK conference call.

What about close()? Since the life cycle of the delegate is managed by the server, and the
life cycle of the proxy is unbounded, close() should probably throw an exception. 

What about commit() and rollback() for Transaction instances obtained from the proxy? Since
the transaction is by definition managed by the server, these methods should throw an exception.

Is the proxy for use only with JTA? Other possible use cases include "extended persistence
context" within the server as well as Java SE. In these cases, where there is no TransactionSynchronizationRegistry
assistance, a ThreadLocal would be needed, and the implementation is not as straightforward.
For example, to support multiple PersistenceManagerFactories, a Map of pmf to pm would be
needed in the ThreadLocal. And the API would need to be told which factory to use.

> 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/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message