On Fri, Aug 21, 2009 at 9:26 AM, Jason Hanna < jason.m.hanna.at.coincid...@gmail.com> wrote:
> > It is *most definitely* a JPA-related issue, either due to a bug or > some configuration minutia. I believe it is simply a matter of state management. OpenJPA can't tell the difference between an unloaded property and a null property. I.e. when your object comes back from AMF, the property is null, but because you've disabled detached state management, there is nothing to tell OpenJPA that the field was deliberately set null vs. the field having not been loaded prior to serialization. I'm sure someone will correct me if I'm wrong. -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:da...@6degrees.com
