Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 58176 invoked from network); 12 Feb 2009 15:23:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Feb 2009 15:23:11 -0000 Received: (qmail 51704 invoked by uid 500); 12 Feb 2009 15:23:09 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 51682 invoked by uid 500); 12 Feb 2009 15:23:09 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 51672 invoked by uid 99); 12 Feb 2009 15:23:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2009 07:23:08 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kevan.miller@gmail.com designates 74.125.46.31 as permitted sender) Received: from [74.125.46.31] (HELO yw-out-2324.google.com) (74.125.46.31) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2009 15:22:58 +0000 Received: by yw-out-2324.google.com with SMTP id 5so399385ywh.85 for ; Thu, 12 Feb 2009 07:22:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:mime-version:subject:date:references :x-mailer; bh=0SfowvvEELHfeD4pn7E8GiE9XZpLIBQtI2ArOoCNc7M=; b=wB35E6z6WoZO1Sx7IxqBgzY8XUAWcbnp+od1ja4PTVADEK79zpN5DwWc51qIHL7RUo 00FnlXVFhhrgnqmL08gMxtpjg6uvJqjkBzD20w/nzmfg4/d5mSjXdhF4zq9XAAZL+K3B 9usahb6i0xzLwwgQzmOvbd8Bhcz8l+bpsCn90= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type:mime-version:subject :date:references:x-mailer; b=pv43vLhxzu4qHUaLxiRq5LcFeYN7phquVxVVpfRwUQcjFVTU/XaB7X3JoxdVL+aM80 LrjtqpXeNOu8DyKf7gMn6wzQh2rSTsQ3ZbUHQkVtyo9XpWP4TiqvwQQMMrsrhJ2yD5BC rt+VHsgzjl8y72LAt/gGAoMvDcEW65Ro52ciA= Received: by 10.100.134.10 with SMTP id h10mr1146825and.68.1234452157822; Thu, 12 Feb 2009 07:22:37 -0800 (PST) Received: from ?10.0.1.190? (cpe-076-182-095-055.nc.res.rr.com [76.182.95.55]) by mx.google.com with ESMTPS id c9sm131476ana.33.2009.02.12.07.22.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 12 Feb 2009 07:22:36 -0800 (PST) Message-Id: <7537CAA7-3B19-4FD8-B145-CF5B8F54A085@gmail.com> From: Kevan Miller To: user@geronimo.apache.org In-Reply-To: <21969527.post@talk.nabble.com> Content-Type: multipart/alternative; boundary=Apple-Mail-143-594401792 Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: OpenJPA problems with multi persistence.xml Date: Thu, 12 Feb 2009 10:22:35 -0500 References: <21969527.post@talk.nabble.com> X-Mailer: Apple Mail (2.930.3) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-143-594401792 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On Feb 11, 2009, at 10:55 PM, bongosdude wrote: > > I posted this problem on openjpa forum: Please see this thread at: > > http://n2.nabble.com/Problem-with-multi-persistence-units-td2303818.html#a2304438 > > > One of OpenJPA developer replied to my post and pointed out some > problem > that may be caused by how geronimo configures openjpa. I copied his > reply > here and hope someone from geronimo developers can comment > > Hi, > It looks like Geronimo might be passing in some extra properties to > OpenJPA??? In the trace, there are two openjpa properties that are > suspect. You don't have them in your persistence.xml. And, if you > are not > passing them in as system properties, then my next guess is > Geronimo. The > two properties that seem to be causing your situation are these: > > openjpa.MetaDataFactory: > jpa(Files=/usr/local/geronimo- > tomcat6-javaee5-2.1.3/repository/default/callingcard-ear/1.0/ > callingcard-ear-1.0.car/callingcard-ejb.jar) > > openjpa.jdbc.SynchronizeMappings: buildSchema(ForeignKeys=true) > > The first one (MetaDataFactory) specifies which persistence types to > process. Since a jar file is specified, we will search the jar file > for any > persistence types (regardless of whether they are listed in a > persistence.xml file or not). Our documentation explains this a bit > more > [1]. I don't know where the MetatDataFactory setting is coming from... I can't find anywhere where it is set by either Geronimo/OpenEJB. Maybe I'm not looking in the right places. > > The next property (SynchronizeMappings) is what I was referring to in > earlier e-mails. This is the property that tells OpenJPA to please > create > the tables if they do not exist. Yes, that's our default setting for SynchronizeMappings. See var/ config/config.xml You can override by adding the following property in your persistence.xml --kevan --Apple-Mail-143-594401792 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
On Feb 11, 2009, = at 10:55 PM, bongosdude wrote:


I = posted this problem on openjpa forum: Please see this thread = at:

http://n2.nabble.com/Problem-with-multi-persistence-units= -td2303818.html#a2304438


One of OpenJPA developer replied = to my post and pointed out some problem
that may be caused by how = geronimo configures openjpa. I copied his reply
here and hope someone = from geronimo developers can comment

Hi,
It looks like = Geronimo might be passing in some extra properties to
OpenJPA??? =  In the trace, there are two openjpa properties that are =
suspect.  You don't have them in your persistence.xml. =  And, if you are not
passing them in as system properties, then = my next guess is Geronimo.  The
two properties that seem to be = causing your situation are these:

openjpa.MetaDataFactory: =
jpa(Files=3D/usr/local/geronimo- =
tomcat6-javaee5-2.1.3/repository/default/callingcard-ear/1.0/callingca= rd-ear-1.0.car/callingcard-ejb.jar) =

openjpa.jdbc.SynchronizeMappings: buildSchema(ForeignKeys=3Dtrue) =

The first one (MetaDataFactory) specifies which persistence = types to
process.  Since a jar file is specified, we will = search the jar file for any
persistence types (regardless of whether = they are listed in a
persistence.xml file or not).  Our = documentation explains this a bit more
[1]. =

I don't know where the = MetatDataFactory setting is coming from... I can't find anywhere where = it is set by either Geronimo/OpenEJB. Maybe I'm not looking in the right = places.


The next property = (SynchronizeMappings) is what I was referring to in
earlier e-mails. =  This is the property that tells OpenJPA to please create
the = tables if they do not exist.

Yes, = that's our default setting for SynchronizeMappings. See = var/config/config.xml

You can override by = adding the following property in your = persistence.xml

<property = name=3D"openjpa.jdbc.SynchronizeMappings" value=3D"false" = />

--kevan
= --Apple-Mail-143-594401792--