Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of brightnesslevels@gmail.com
 designates 209.85.218.213 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=mShf0LS+E3CHgafiaMGLWtKldBIBBoWRNfhFWqKo3Mqbhh7LZXqgSFbX8GGL+ORd4B
         0WBsJ7AtcjScm4yIbrV2eELZKfVgh4Zr+nCmLnBj4/Kmal+L9NBzd7QGGXyKsUlxlbzL
         Z/ksOUWOHub09ZOES4VUKnI5JuvSOgOV39Blg=
MIME-Version: 1.0
In-Reply-To: 
 <6248F687D9D2504B8EF10DA7AA6955B6010082627FCC@HEX-CLUSTERING.hex2007.local>
References: 
 <6248F687D9D2504B8EF10DA7AA6955B6010082627F7E@HEX-CLUSTERING.hex2007.local>
	<510143ac0905270247x65f747fftcfdbbf25ff8a86fa@mail.gmail.com>
	<6248F687D9D2504B8EF10DA7AA6955B6010082627FCC@HEX-CLUSTERING.hex2007.local>
From: Sergey Podatelev <brightnesslevels@gmail.com>
Date: Wed, 27 May 2009 15:53:04 +0400
Message-ID: <8752ef10905270453j38189c66n82cf9326c4e5bc46@mail.gmail.com>
Subject: Re: How to handle XA Transactions?
To: users@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Check this out:
http://th1rty7.blogspot.com/2009/03/spring-distributed-transactions-across.=
html

On Wed, May 27, 2009 at 3:39 PM, Peter Henzler <phe@scodi.ch> wrote:
> Hi Jukka
>
> Thank you for the reply.
>
>> The sessions you get from the Repository.login() method from
>> Jackrabbit implement the org.apache.jackrabbit.api.XASession
>> interface, whose getXAResource() method can be used to attach the
>> session to a distributed XA transaction.
>
>> The nice thing about the JCA packaging is that it handles the
>> XAResource part automatically for you, but there's nothing stopping
>> you from doing the same with a little bit of code also in other
>> deployment scenarios.
>
> Do you mean code like this?:
>
> =A0 =A0 =A0 =A0Transaction tx =3D tm.getTransaction(); // get the running=
 javax.transaction.Transaction
> =A0 =A0 =A0 =A0XASession session =3D (XASession)repository.login(creds, r=
ename);
> =A0 =A0 =A0 =A0XAResource res =3D session.getXAResource();
> =A0 =A0 =A0tx.enlistResource(res);
> =A0 =A0 =A0 =A0// do changes in repository through the session interface
> =A0 =A0 =A0session.logout();
> =A0 =A0 =A0tx.delistResource(res, XAResource.TMSUCCESS);
>
> Or what code do you mean?
>
> Would that be enough for committing the repository changes when the globa=
l container managed XA Transaction with changes of other database connectio=
ns get commited or to get rollbacked if one of those others throws an exept=
ion?
>
>
>
>
>
>>> If I am using the Jackrabbit Datastore and Persistence configured with =
an XA
>>> JDBC-Driver, do I really need Transactions in Jackrabbit. Wouldn't the =
XA
>>> JDBC-Driver work in a 2phase commit handled by the installed JTA
>>> TransactionManager ?
>
>>No. Jackrabbit expects to be in full control of the underlying
>>database connection, so having it included in an externally managed
>>transaction is not a good idea. We've seen quite a few problems caused
>>by this.
>
> Ok, I unterstand that Jackrabbit want it's own database connection that i=
s not used by anyone else.
> You mean that the configured JDBC Driver for the Jackrabbit repository sh=
ould be a normal JDBC Driver instead of a XA JDBC Driver?
>
> Best regards
> Peter
>


--=20
sp