Return-Path: 
 <users-return-7027-apmail-openjpa-users-archive=openjpa.apache.org@openjpa.apache.org>
Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org
Received: (qmail 78631 invoked from network); 3 May 2010 18:39:46 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 3 May 2010 18:39:46 -0000
Received: (qmail 67111 invoked by uid 500); 3 May 2010 18:39:45 -0000
Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org
Received: (qmail 67086 invoked by uid 500); 3 May 2010 18:39:45 -0000
Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@openjpa.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@openjpa.apache.org>
List-Post: <mailto:users@openjpa.apache.org>
List-Id: <users.openjpa.apache.org>
Reply-To: users@openjpa.apache.org
Delivered-To: mailing list users@openjpa.apache.org
Received: (qmail 67078 invoked by uid 99); 3 May 2010 18:39:45 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 18:39:45 +0000
X-ASF-Spam-Status: No, hits=1.4 required=10.0
	tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of michael.d.dick@gmail.com
 designates 209.85.218.227 as permitted sender)
Received: from [209.85.218.227] (HELO mail-bw0-f227.google.com)
 (209.85.218.227)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 18:39:40 +0000
Received: by bwz27 with SMTP id 27so1662325bwz.33
        for <users@openjpa.apache.org>; Mon, 03 May 2010 11:39:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:mime-version:received:in-reply-to
         :references:from:date:message-id:subject:to:content-type;
        bh=Y0AROmQ/kXBofHGooV270RlLqcOgsZbLOjXUGcOxTh0=;
        b=i77u4eH4HAyNYV+dpWwfA9mzYaX2+LMMJq3MDfIuO3Q7R/h7UxARA9b9qES+GsHS8v
         F84ODROS4QmKQiC9TttZMj3HGu5wCASc/kWC9GnEW7FS86wAu2xcd88Li1PB+EcO1qtO
         ZJwHMbLbE41+t6IzjMdcLoD+ur/m+QycwCj34=
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;
        b=WbzxzrTgUkKg+R0GH7SkLm/Ix1fHhOHUubihau1C1XtigdalRFPcwGq8+iTLf54MDk
         l0ydhfbof5rNwrLKmKTPLksfn8VO4VmCegAvVNWaUmV4uQY4xRJl5VdjCx4MZXJMYEE2
         mbz89Mx+nWu1wLX7TCvi64o8qyOEf92ZBs1qw=
Received: by 10.204.133.129 with SMTP id f1mr4700148bkt.45.1272911957305;
 Mon,
	03 May 2010 11:39:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.54.142 with HTTP; Mon, 3 May 2010 11:38:57 -0700 (PDT)
In-Reply-To: <1272491939487-4977174.post@n2.nabble.com>
References: <1271755942291-4930234.post@n2.nabble.com>
 <y2lf8b633141004200654w3d20155kcb4628c839d96e52@mail.gmail.com>
	<1271920255857-4941281.post@n2.nabble.com>
 <u2m72c1350f1004281346ic8a3731wf5a116c51fb571ff@mail.gmail.com>
	<1272491939487-4977174.post@n2.nabble.com>
From: Michael Dick <michael.d.dick@gmail.com>
Date: Mon, 3 May 2010 13:38:57 -0500
Message-ID: <y2h72c1350f1005031138o9ec9e9eyd7d235ee68904910@mail.gmail.com>
Subject: Re: OpenJPA without jta-data-source in persistence xml
To: users@openjpa.apache.org
Content-Type: multipart/alternative; boundary=00151747913812e2580485b4e927

--00151747913812e2580485b4e927
Content-Type: text/plain; charset=ISO-8859-1

Hi Pinaki,

Thanks for looking into this. I was hoping it'd be relatively
straight-forward to implement. I do have a couple of minor questions
though:

1.) Is the jta-data-source needed in your example :
      <jta-data-source>jdbc/slice-ds1</jta-data-source>

           <properties>
                <property name="openjpa.BrokerFactory" value="slice"/>
                <property name="openjpa.slice.Names"
value="slice1,slice2,slice3"/>
                <property name="openjpa.slice.Master" value="slice1"/>
                <property name="openjpa.slice.slice1.ConnectionFactoryName"
value="jdbc/slice-ds1"/>
                <property name="openjpa.slice.slice2.ConnectionFactoryName"
value="jdbc/slice-ds2"/>
                <property name="openjpa.slice.slice3.ConnectionFactoryName"
value="jdbc/slice-ds3"/>
                <property name="openjpa.TransactionMode" value="managed" />
               <property name="openjpa.ConnectionFactoryMode"
value="managed" />
        </properties>

It seems we could either omit the jta-data-source, or infer that it is the
master slice if it is present.  Maybe a better question is, what would
happen if the jta-data-source and the master slice were different?

2.) If the entity manager is JTA scoped, then openjpa.TransactionMode and
openjpa.ConnectionFactoryMode should already be set to managed. Is there
anything in slice that would require them to be set?

Regards,
-mike

-mike

On Wed, Apr 28, 2010 at 4:58 PM, Pinaki Poddar <ppoddar@apache.org> wrote:

>
> Slice currently does not recognize configured JNDI-registered data sources.
> The only existing way is to configure each slice via an explicit connection
> url.
> Here is a proposal to allow better configuration in JEE.
>
>          https://issues.apache.org/jira/browse/OPENJPA-1643
>
> -----
> Pinaki
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/OpenJPA-without-jta-data-source-in-persistence-xml-tp4930234p4977174.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>

--00151747913812e2580485b4e927--