> like i said before > " DataNucleus has no way of "seeing" > the changes you make to the internal values of a serialized field, and as a > result it doesn't know when it needs to flush changes to these fields to the > datastore. However, DataNucleus *can* see when the top-level serialized > field reference changes."
DataNucleus loads the Map field in the first place, so replaces it with a wrapper and intercepts all mutator methods. This ought to be present in the log. Any mutator call will make that field in the owner object dirty, also in the log. This dirty field will cause an update, in the log. Hence why I said look at the log to debug your problem. GAE/J not wrapping the Map field would be a bug in GAE/J's plugin (if it is that that is the problem). -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
