I hit this problem a couple of months ago and discovered it happens if you serialize the object because the serialize/deserialize process seems to lose track of null values. There is an openjpa setting which fixes this but my problem was that I mistakenly had a remote interface to my ejb instead of a local interface (simply @Remote instead of @Local) and the remote interface was causing the serialization to occur. When I switched to a local interface there was no serialization of the persistent objects and the null value was correctly saved.
So, in brief, it is worth checking first of all that you are not accidentally serializing the persistent objects and if you need to serialize them there is a setting which will make it all work correctly - I would have to dig around to find the setting. Regards Martin -- View this message in context: http://n2.nabble.com/null-values-not-updating-tp3224059p3232848.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
