Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 85084 invoked from network); 15 Jun 2006 18:53:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Jun 2006 18:53:36 -0000 Received: (qmail 47344 invoked by uid 500); 15 Jun 2006 18:53:34 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 47309 invoked by uid 500); 15 Jun 2006 18:53:34 -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 47300 invoked by uid 99); 15 Jun 2006 18:53:33 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 11:53:33 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of edgarpoce@gmail.com designates 66.249.92.169 as permitted sender) Received: from [66.249.92.169] (HELO ug-out-1314.google.com) (66.249.92.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 11:53:32 -0700 Received: by ug-out-1314.google.com with SMTP id a2so357381ugf for ; Thu, 15 Jun 2006 11:53:11 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CfZ6dT6bYOan0kYCJxhBH1IqOZgnUOX5pgdE/DyVuSHkXUaoMmW+44D6P0FcIYDAayscB9HFLXn3DVnE0ad1Ba6SVmp2Oa/fpd9tY5lrStO9fuhyPFeawL+PS2rBwCAbis8cc5JkUZVT+jetFb/zwscZ67vBvxMGlvM8BfgxQuA= Received: by 10.67.103.7 with SMTP id f7mr2002629ugm; Thu, 15 Jun 2006 11:53:11 -0700 (PDT) Received: by 10.67.30.15 with HTTP; Thu, 15 Jun 2006 11:53:11 -0700 (PDT) Message-ID: <8a83c96b0606151153w1899804fl5d2e720184db41d2@mail.gmail.com> Date: Thu, 15 Jun 2006 15:53:11 -0300 From: "Edgar Poce" To: dev@jackrabbit.apache.org Subject: Re: question reagrding JNDI datasource In-Reply-To: <040901c690a0$bd85afa0$b6fdfe0a@gkaradimitr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8a83c96b0606150636r41a8ee77m695815fea3c2de73@mail.gmail.com> <040901c690a0$bd85afa0$b6fdfe0a@gkaradimitr> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Giota, On 6/15/06, Giota Karadimitriou wrote: > Thanks, but the reason for me to use JCA in the first place was in order > to have container managed JTA transactions. AFAIK the JCA project will handle that, the underlying connection is an internal resource and must not participate in JTA transactions. > I wanted a session bean to > call jackrabbit repository (wrapped as RAR) perform some operation and > when the EJB finishes, the container (application server) would commit > or rollback the transaction. > btw, take a look to the message I sent yesterday about some problems in the jca connector. br, edgar > > -----Original Message----- > > From: Edgar Poce [mailto:edgarpoce@gmail.com] > > Sent: Thursday, June 15, 2006 4:37 PM > > To: dev@jackrabbit.apache.org > > Subject: Re: question reagrding JNDI datasource > > > > Hi > > > > On 6/15/06, Jukka Zitting wrote: > > > Hi, > > > > > > On 6/14/06, Giota Karadimitriou > wrote: > > > > I would just like to report that it is not feasible to use > datasource > > > > with JCA and this because of line 339 in > DatabasePersistenceManager > > > > which performs an explicit con.commit(); > > > > > > > have you tried to configure the datasource that uses jackrabbit's > > persistence manager to not take part of JTA transactions? > > > > In jboss you can configure it the datasource deployment descriptor > > with a tag called "no-tx-datasource". See > > http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources > > > > br, > > edgar > > > > > Could you file a Jira issue about this? I'm not sure if we can (or > > > should) fix this right away without having to refactor extensively > as > > > the current database pm treats the underlying database as an > internal > > > resource that is not part of a higher-level transaction. In any case > > > it would be good to have a persistent reminder about the issue, even > > > if we decide to resolve it as Won't fix. > > > > > > BR, > > > > > > Jukka Zitting > > > > > > -- > > > Yukatan - http://yukatan.fi/ - info@yukatan.fi > > > Software craftsmanship, JCR consulting, and Java development > > > > >