Well, it should be pretty much as simple for me. That's why I can't find a solution for that problem.
org.datanucleus.ObjectManagerImpl close: Outstanding nontx update being committed to datastore just means it commits something. I have tried invoking setter later too [as it was mentioned here: http://gae-java-persistence.blogspot.com/2009/10/serialized-fields.html that DataNucleus may not see changes to serialized fields], but same result. On Oct 25, 2:51 pm, Broc Seib <broc.s...@gmail.com> wrote: > There's this > thread:http://groups.google.com/group/google-appengine-java/browse_thread/th... > > Might I add, I wrestled with using JDO for several months before I > realized it was just not a good fit for AppEngine's DataStore. I > switched to Objectify and life has been much better since. Now I don't > have to try to envision things from Data Nucleus point of view, but > rather just think like datastore to begin with. > > Broc > > On Oct 24, 5:33 am, Paul <pgronkiew...@gmail.com> wrote: > > > Hmm... no ideas anyone? I have tried to google for hours and no > > results. I really don't understand why that problem exists. -- 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-java@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.
