Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of mprudhomapache@gmail.com
 designates 64.233.162.232 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=N+YwNjnjW3XOrJfwzIIhI36D8jD1+CfYolcM5rlKGdajsxzbXpBZJEzd66VAYTyy30giBWd0QNCINQrG2RdjN2f6ZccettHqWSxSV02UcWzgMZoi5pSzEstE1u28L+F1W8NAmWhMMLcyz0i3d3HM8jANpQuOSVx3BO6+3z7pCjg=
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <7262f25e0708080911n236a0335w8130e45730a2343c@mail.gmail.com>
References: <7262f25e0708080911n236a0335w8130e45730a2343c@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CF51AE8D-32D3-4740-8539-6E7CFED9B505@apache.org>
Content-Transfer-Encoding: 7bit
From: Marc Prud'hommeaux <mprudhom@apache.org>
Subject: Re: OpenJPAPersistence extends Persistence; should we remove this?
Date: Wed, 8 Aug 2007 09:29:39 -0700
To: dev@openjpa.apache.org
Sender: Marc Prud'hommeaux <mprudhomapache@gmail.com>

Patrick-

I don't know anything about the nature of the problems with the  
Persistence provider registry, but I don't see any reason why  
OpenJPAPersistence should need to extend Persistence.

However, I can't imagine how simply removing the inheritance  
connection would solve anything. Are you suggesting that we replicate  
the Persistence functionality (like createEntityManagerFactory()) in  
our own OpenJPAPersistence class?


On Aug 8, 2007, at 9:11 AM, Patrick Linskey wrote:

> Hi,
>
> We've run into a couple of problems with the static registry
> maintained in the Persistence class. Should we isolate ourselves from
> it by making OpenJPAPersistence not extend Persistence? If we did so,
> it would be pretty straightforward for OpenJPA to never reference
> Persistence, which would mean that people who ran into trouble with
> that class could work around the problems by using OpenJPA APIs
> instead.
>
> Thoughts?
>
> -Patrick
>
> -- 
> Patrick Linskey
> 202 669 5907