Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 34375 invoked from network); 22 Dec 2006 11:06:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Dec 2006 11:06:45 -0000 Received: (qmail 31902 invoked by uid 500); 22 Dec 2006 11:06:52 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 31891 invoked by uid 99); 22 Dec 2006 11:06:52 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Dec 2006 03:06:52 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Dec 2006 03:06:43 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 85F397142A1 for ; Fri, 22 Dec 2006 03:06:23 -0800 (PST) Message-ID: <17655904.1166785583546.JavaMail.jira@brutus> Date: Fri, 22 Dec 2006 03:06:23 -0800 (PST) From: "Guido Anzuoni (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Commented: (JDO-445) Add convenience method that returns a PersistenceManager proxy In-Reply-To: <14512559.1165610180975.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/JDO-445?page=comments#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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira