[appengine-java] Re: Forcing update of JPA entity

2010-01-21 Thread datanucleus
> When I do this, the main entity will not be updated in the datastore > since I never actually modified the member itself Shouldn't make the slightest bit of difference. GAE/J ought to replace that List with a wrapper that intercepts update operations. It hasn't done that. http://code.google.com/

[appengine-java] Re: Forcing update of JPA entity

2010-01-21 Thread Elias Mårtenson
On 22 Jan, 00:26, datanucleus wrote: > Shouldn't make the slightest bit of difference. GAE/J ought to replace > that List with a wrapper that intercepts update operations. It hasn't > done > that.http://code.google.com/p/datanucleus-appengine/issues/detail?id=144&c... Thanks for the information

[appengine-java] Re: Forcing update of JPA entity

2010-01-21 Thread datanucleus
> Your workarund, to use JDOHelper would be what I need, but I'm not > using JDO. I'm using JPA. Is there a similar workaround there? Doesn't make any difference either. JPA (in DataNucleus) uses JDO enhancement, and so marking the field as dirty using a JDO helper method would do the same under J

[appengine-java] Re: Forcing update of JPA entity

2010-01-21 Thread Elias Mårtenson
On Jan 22, 2:16 pm, datanucleus wrote: > > Your workarund, to use JDOHelper would be what I need, but I'm not > > using JDO. I'm using JPA. Is there a similar workaround there? > > Doesn't make any difference either. JPA (in DataNucleus) uses JDO > enhancement, and so marking the field as dirty u

[appengine-java] Re: Forcing update of JPA entity

2010-01-21 Thread Bert Peters
JDO does not do this too. I think it is a rather annoying bug. Serializing does not work (use that too myself) and just modifing an element does not work too, as your program clearly found out. Still waiting for a fix though... On Jan 22, 12:50 am, Elias Mårtenson wrote: > On 22 Jan, 00:26, datan