Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 45448 invoked from network); 13 May 2005 10:25:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 May 2005 10:25:35 -0000 Received: (qmail 16897 invoked by uid 500); 13 May 2005 10:29:50 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 16882 invoked by uid 99); 13 May 2005 10:29:49 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from anchor-post-31.mail.demon.net (HELO anchor-post-31.mail.demon.net) (194.217.242.89) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 13 May 2005 03:29:49 -0700 Received: from bladesys.demon.co.uk ([80.177.16.106] helo=[192.168.0.8]) by anchor-post-31.mail.demon.net with esmtp (Exim 4.42) id 1DWXJ9-000Ec2-41 for jackrabbit-dev@incubator.apache.org; Fri, 13 May 2005 10:22:15 +0000 Message-ID: <42848135.5000909@bladesystems.co.uk> Date: Fri, 13 May 2005 11:28:05 +0100 From: Sean Radford User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: jackrabbit-dev@incubator.apache.org Subject: Re: JDBC PersistenceManager References: <42832C84.4070105@bladesystems.co.uk> <42837DC4.7050005@gmail.com> In-Reply-To: <42837DC4.7050005@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Edgar Poce wrote: > Hi > > Sean Radford wrote: > >> I seem to remeber a message on the list a few weeks back about a JDBC >> PersistenceManager. Anyone know anything about it? > > I've just uploaded a few changes. See JCR-91 in JIRA. But it's not > ready for use because: > ... Cool. I'll hopefully get to play with it next week. Just had a tiny peek at the code though, and have one quick question.. If one is using a managed transaction (most probably via the JNDIConnectionFactory should the PM be calling Connection.commit() in the store(ChangeLog) method? Regards, Sean -- Dr. Sean Radford, MBBS, MSc sradford@bladesystems.co.uk http://bladesys.demon.co.uk/