[appengine-java] Re: JDO doesn't save every modification

2010-01-19 Thread Bert Peters
The type returned is "class java.util.ArrayList". Is there a possible way to fix this? On Jan 19, 8:30 pm, datanucleus wrote: > Look in the log (at DEBUG level) and see if the List field is replaced > by a wrapper type when you retrieve the overall object from the > datastore. Alternatively, prin

[appengine-java] Re: JDO doesn't save every modification

2010-01-19 Thread datanucleus
Look in the log (at DEBUG level) and see if the List field is replaced by a wrapper type when you retrieve the overall object from the datastore. Alternatively, print out the getClass() of the List object before your update. If it isn't of type "org.datanucleus.sco." then the error is in GAE/J

[appengine-java] Re: JDO doesn't save every modification

2010-01-19 Thread Bert Peters
Ok, here is the rest. Sorry about the bad problem definition: Basically, it's like this. (cp.base is an instance of the before mentioned Base class) Integer cb = this.base.getCurrentBuild(); cp.base.setBuildings(cb , this.base.getBuildings(cb) + 1);

[appengine-java] Re: JDO doesn't save every modification

2010-01-19 Thread datanucleus
Define "updates" with respect to that field. Saying you change something is one thing, but posting the code that changes that thing is a prerequisite to any comment. Obviously the log would also tell you plenty about that field, like is it replaced by a proxy/wrapper when it is read in ? -- You re

[appengine-java] Re: JDO doesn't save every modification

2010-01-19 Thread Bert Peters
Then source code it is: Source for the involved class: package elemental.data; import java.util.ArrayList; import java.util.Date; import java.util.List; import javax.jdo.PersistenceManager; import javax.jdo.Query; import javax.jdo.annotations.IdGeneratorStrategy; import javax.jdo.annotations.Id

Re: [appengine-java] Re: JDO doesn't save every modification

2010-01-19 Thread Raphael André Bauer
On Tue, Jan 19, 2010 at 4:55 PM, Bert Peters wrote: > Alright, here we go. > Somewhere in execution, 2 dates, 4 double fields and an integer list > are updated to new values. During checkup in the rest of the program, > everything seems OK. > Then, upon finish, at pm.close(), all updated variables

[appengine-java] Re: JDO doesn't save every modification

2010-01-19 Thread Bert Peters
Alright, here we go. Somewhere in execution, 2 dates, 4 double fields and an integer list are updated to new values. During checkup in the rest of the program, everything seems OK. Then, upon finish, at pm.close(), all updated variables are saved, except for the integer list. Enough information? O