Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 30480 invoked from network); 6 Aug 2007 14:12:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Aug 2007 14:12:30 -0000 Received: (qmail 98019 invoked by uid 500); 6 Aug 2007 14:12:28 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 97993 invoked by uid 500); 6 Aug 2007 14:12:28 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 97984 invoked by uid 99); 6 Aug 2007 14:12:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Aug 2007 07:12:28 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [62.192.10.254] (HELO goobak01.day.com) (62.192.10.254) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Aug 2007 14:12:24 +0000 Received: by goobak01.day.com (Postfix, from userid 1212) id B2A6E5086E; Mon, 6 Aug 2007 16:06:40 +0200 (CEST) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.185]) by goobak01.day.com (Postfix) with ESMTP id 22FA650868 for ; Mon, 6 Aug 2007 16:06:39 +0200 (CEST) Received: by rv-out-0910.google.com with SMTP id k20so1129948rvb for ; Mon, 06 Aug 2007 07:12:00 -0700 (PDT) Received: by 10.114.111.1 with SMTP id j1mr5663240wac.1186409520481; Mon, 06 Aug 2007 07:12:00 -0700 (PDT) Received: by 10.114.190.8 with HTTP; Mon, 6 Aug 2007 07:12:00 -0700 (PDT) Message-ID: Date: Mon, 6 Aug 2007 16:12:00 +0200 From: "Dominique Pfister" Sender: dpfister@day.com To: dev@jackrabbit.apache.org Subject: Re: Questions about TX in Jackrabbit, JTA and Spec compliance In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: b92d1402c85daca2 X-Virus-Checked: Checked by ClamAV on apache.org On 8/6/07, Cris Daniluk wrote: > > If the DBMS supports the two-phase transaction (I believe Postgres > does), then you could just use a JTA-enabled version of the JDBC > driver and register the DB transaction to the existing XA. How would you do that, technically, if everything you have at hand is your own XAResource implementation? Am I missing some important information the TM is giving me about the current transaction and some way to dynamically register new resources? > > The only other option is to persist the changelog, effectively > converting it into a journal. However, I think bringing the DBMS into > the XA is probably the quickest way to solve this problem.. > Hm, I doubt that. JR at its core stores content with calls to an abstract interface, namely the Persistence Manager. It is this component that may store nodes and properties inside a DBMS, via JDBC calls over a single connection it acquired on startup. Changing this to using a transaction-local JDBC connection looks more complex to me than persisting the change log. Dominique