Detecting null fields during re-attachment is tricky. How do you know if the field was null'd out explicitly, or if it was never filled in in the first place? OpenJPA has attempted to provide the facilities for detecting these conditions [1]. In the referenced section, it discusses how you can configure your application to do the "proper" amount of detection. As you will read, there may be some performance concerns with some of the processing, so you have to evaluate your application's requirements before just blindly turning these options on or off.
[1] http://openjpa.apache.org/builds/1.2.1/apache-openjpa-1.2.1/docs/manual/manual.html#ref_guide_detach On Wed, Jul 8, 2009 at 11:24 AM, Daryl Stultz <[email protected]> wrote: > On Wed, Jul 8, 2009 at 9:05 AM, Rick Curtis <[email protected]> wrote: > > > Chris- > > > > You may want to try adding a @Version field to your Entity. > > > > I've overcome the problem without any @Version annotations (and no > LockManager). I'm still interested in the cause of the Chris's problem. As > well, an explanation of why @Version would fix things would be helpful. > > -- > Daryl Stultz > _____________________________________ > 6 Degrees Software and Consulting, Inc. > http://www.6degrees.com > mailto:[email protected] >
