Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of pawel.veselov@gmail.com
 designates 209.85.212.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1325540472360-7144915.post@n2.nabble.com>
References: 
 <CAMnJ+BfBCc_XgexcH=Q6JjY2bQ4QTdemXE2Mb1wQWFLff_3aYA@mail.gmail.com>
 <1325540472360-7144915.post@n2.nabble.com>
From: Pawel Veselov <pawel.veselov@gmail.com>
Date: Mon, 2 Jan 2012 15:23:13 -0800
Message-ID: 
 <CAMnJ+Bcspg8bH=sXdgmULjxxX8sev=9BLGLo8abYTDYAo3EY0w@mail.gmail.com>
Subject: Re: changing specific openjpa.jdbc.DBDictionary
To: users@openjpa.apache.org
Content-Type: multipart/alternative; boundary=20cf307d072c1247c804b593df85

--20cf307d072c1247c804b593df85
Content-Type: text/plain; charset=UTF-8

On Mon, Jan 2, 2012 at 1:41 PM, Pinaki Poddar <ppoddar@apache.org> wrote:

> Nope, sorry.
> For a different database (with a different URL), you will require a
> different persistence.xml anyway.
>
> I disagree. There is nothing in persistence.xml that requires to hardcode
the database URL. It's actually quite a bad taste to do so (IMHO).
Persistence.xml supposedly points to the JNDI name that will resolve to a
data source, which is configured outside of application.

It would  be nice if it were to be possible to specify properties for a
specific dictionary.
The same way OpenJPA supports multiple databases, a portable J2EE
application should be able to too :)

--20cf307d072c1247c804b593df85--