Alright I just didn't realize datastore datanucleus plugin was the
responsibility of the google team.
I created some issues:
http://code.google.com/p/googleappengine/issues/detail?id=2501
http://code.google.com/p/googleappengine/issues/detail?id=2502
Well the message just before ATTENTION: Meta-data warning for
com (see http://tinypaste.com/c2590) is that:
INFO: Performing appengine-specific metadata validation for
com.testgae.xp.domain.B
9 déc. 2009 20:48:57 org.datanucleus.store.appengine.MetaDataValidator
warn
So don't you think it
Hi Tim,
Ithink you ran into the same problem as me. You can see in my post
(http://groups.google.com/group/google-appengine-java/browse_thread/
thread/a0be8114353d9798/c3b9e94f1942d661?lnk=gstq=entity+updated
+twice#c3b9e94f1942d661) an example where I just call make persistence
once on an
not solve my problem (only setting
the child keys by hand which is not that great...).
On 5 déc, 19:34, Ratamovic ratamo...@gmail.com wrote:
Hi everybody,
My model contains a Class A ---Bidi one to many--- B ---one to
many--- C ---one to one--- D.
I wrote 3 unit tests with appengine 1.2.8 and JDO
Thx for your answer. To clarify these points:
1- The transaction is really a JDO/datastore exception encapsulated by
Spring (as I am using the transactional components of Spring). To be
sure, I tried to execute these tests with manual transactions instead
of not Spring and the result was the same
