> -----Original Message-----
> From: Gordon Yorke [mailto:gordon.yorke_at_oracle.com]
> Sent: Saturday, 7 July 2007 3:54 AM
> To: users_at_glassfish.dev.java.net
> Subject: RE: Lazy OneToOne with composite key failing
>
> What is your deployment environment? Do other entities in
> your persistence unit have lazy relationships? Is it only
> the read-only mapping that is failing with this error?
> --Gordon
Sorry I just read another thread "Problem deploying ManyToOne
lazy-fetched Entities", and can confirm that if I turn off the verifier
in GF it deploys as expected with a @OneToOne with fetch=FetchType.LAZY.
Just for the record though I deploy via Ant to a local GF, and had the
verify="true" value set. @OneToMany's didn't appear to be an issue. I've
just gone through and set the lazy fetch type on the remaining
@ManyToOne's and its deployed and working fine now without the verifier.
Regards
Joe
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.