[ http://issues.apache.org/jira/browse/JDO-445?page=comments#action_12459912 ] Jörg von Frantzius commented on JDO-445: ----------------------------------------
And what about non-transactional reads? What we do in our systems is to keep track of one PM per thread in a Map, and upon returning a PM, we iterate the keyset() of threads in this map, "reaping" dead threads by closing their PMs if they weren't closed already, and removing found dead threads from the Map afterwards. As far as I can see, this could provide an implementation of the proposed methods, as with an ongoing transaction the current thread is equivalent to the ongoing transaction. The only problem could be transactions that (sequentially) span multiple threads, but I don't believe that any XA implementation supports that scenario anyway. > 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
