Re: detachment, getReference(), and openjpa.DetachState

2007-01-18 Thread Kevin Sutter
On 1/17/07, Dain Sundstrom [EMAIL PROTECTED] wrote: I think we should ask our selves, what does a user expect to happen and make that the default. If every JPA implements this with the loaded+fetchgroup style by default, and OpenJPA doesn't that would be quite surprising to users and will

Re: detachment, getReference(), and openjpa.DetachState

2007-01-17 Thread Craig L Russell
Here's what the spec says about getReference. /** * Get an instance, whose state may be lazily fetched. * If the requested instance does not exist in the database, * the EntityNotFoundException is thrown when the instance *state is first accessed.(The persistence provider runtime is *

RE: detachment, getReference(), and openjpa.DetachState

2007-01-17 Thread Patrick Linskey
The tests can be made to pass by setting the openjpa.DetachState property to 'fgs', 'loaded' is the proper default. If the CTS is relying on any state being loaded after a call to getReference(), then those CTS tests are wrong and should be reported as such. The description of

Re: detachment, getReference(), and openjpa.DetachState

2007-01-17 Thread Dain Sundstrom
On Jan 17, 2007, at 12:07 PM, Patrick Linskey wrote: The tests can be made to pass by setting the openjpa.DetachState property to 'fgs', 'loaded' is the proper default. If the CTS is relying on any state being loaded after a call to getReference(), then those CTS tests are wrong and should