I'm interested in hearing what you would like to see with regard to
entities after the persistence context in which they were valid no
longer exists.
Thanks,
Craig
On May 28, 2010, at 7:18 AM, C N Davies wrote:
Darryl is right, I fought with this one for some time then it dawned
upon me
that I was dealing with a detached entity that had a lazy loaded
field. The
result of toString is like picking the lottery numbers.. pot luck!
Now do
the same thing with runtime enhancement during development and
deploy it
with build time enhancement.
Yet another reason to drag the JPA spec into the 20th century and do
away
with this whole attached / detached state business.
Chris
-----Original Message-----
From: Daryl Stultz [mailto:[email protected]]
Sent: Friday, 28 May 2010 10:23 PM
To: [email protected]
Subject: Re: equals, hashcode, toString, etc, and field access
On Thu, May 27, 2010 at 8:49 PM, Trenton D. Adams
<[email protected]>wrote:
I mean I know if I'm doing lazy loading, toString won't get all the
data,
cause it hasn't been enhanced.
Assuming the object is detached, yes. I believe the JPA spec does not
specify the behavior for attempted access of an unloaded property on a
detached entity. I believe OpenJPA returns null. This makes it very
difficult to tell if an association is null or not loaded. I have
configured
OpenJPA to disallow access to unloaded properties of detached
entities to
avoid the confusion. This means a toString method like yours in my
project
could crash.
--
Daryl Stultz
_____________________________________
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
http://www.opentempo.com
mailto:[email protected]
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
