Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 84405 invoked from network); 29 Aug 2007 19:26:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Aug 2007 19:26:18 -0000 Received: (qmail 15215 invoked by uid 500); 29 Aug 2007 19:26:11 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 15190 invoked by uid 500); 29 Aug 2007 19:26:11 -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 15179 invoked by uid 99); 29 Aug 2007 19:26:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2007 12:26:11 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2007 19:27:04 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1IQTAf-00050O-8C for user@geronimo.apache.org; Wed, 29 Aug 2007 12:25:45 -0700 Message-ID: <12393956.post@talk.nabble.com> Date: Wed, 29 Aug 2007 12:25:45 -0700 (PDT) From: Java_James To: user@geronimo.apache.org Subject: Re: JPA issue when migrating to geronimo 2.0.1 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: james-junk@rogers.com References: <12390954.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org djencks wrote: > > What is your persistence.xml? > Thanks for your quick reply. I actually solved my problem shortly after posting. Just in case anyone else is having this problem it seems that geronimo 2.0.1 has a problem auto loading the geronimo transaction manager. I added the following properties to my persistence.xml and it started working just fine -- View this message in context: http://www.nabble.com/JPA-issue-when-migrating-to-geronimo-2.0.1-tf4348941s134.html#a12393956 Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.