Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of plinskey@bea.com designates
 63.96.176.25 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: openjpa.Id property
Date: Thu, 9 Nov 2006 14:19:04 -0800
Message-ID: <7D856CDFE035FF45A0420ACBD71BDD63026A8E73@repbex02.amer.bea.com>
Thread-Topic: openjpa.Id property
Thread-Index: AccETREBkFWUOzuuQ4ylvH/wQk+L2A==
From: "Patrick Linskey" <plinskey@bea.com>
To: <open-jpa-dev@incubator.apache.org>

Hi,

It's useful in a number of places to get an identifier for a particular
Configuration. For example, as we discussed a few months ago, it would
be useful if the logging subsystem automatically wrote the persistence
unit's ID along with log messages if no such ID was specified in the log
configuration.

Any objections to such an addition? In a JPA environment, this would
correspond to the persistence unit's unitName attribute.

Any suggestions for a better name than openjpa.Id for the property? This
would result in an OpenJPAConfiguration.getId() method call that
returned a String.

-Patrick

--=20
Patrick Linskey
BEA Systems, Inc.=20

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.