[appengine-java] Re: Using entity.setProperty on one-to-many relationships

2010-12-29 Thread Didier Durand
Hi, Yes, the class Entity by Google only supports the core types defined in the Dev Guide. 1 question : it seems that you are trying to mix high-level (JDO) and low-level datastore api. Is that correct ? Why do you have to do that ? regards didier On 29 déc, 10:06, Kalyan Akella

[appengine-java] Re: Using entity.setProperty on one-to-many relationships

2010-12-29 Thread Kalyan Akella
Hi, Yes, I had to use the low level API because that code is part of another unit test I am writing against my domain. So, I had to get hold of the DataStoreService, Entity and such classes, as documented

[appengine-java] Re: Using entity.setProperty on one-to-many relationships

2010-12-29 Thread Didier Durand
Hi, Yes: why don't you only work with JDO and use its persistence manager to store your entities? The pm of jdo will handle translation between annotated pojos and datastore transparently for you and then drastically reduce your code size. N.B; I personnally switched from JDO to Objectify: much

[appengine-java] Re: Using entity.setProperty on one-to-many relationships

2010-12-29 Thread Kalyan Akella
Hi Didier, Thank you for pointing out the easier approach of using JDO PersistenceManager APIs to do unit testing. I missed the point that the same benefits provided by these high-level APIs are equally applicable for unit testing as well. I wrote that code basing purely on the official

[appengine-java] Re: Using entity.setProperty on one-to-many relationships

2010-12-28 Thread Didier Durand
Hi, I think we need to know your class Entity to spot the problem regards didier On Dec 29, 1:57 am, Kalyan Akella kalyan.ake...@gmail.com wrote: Hi, In my application, I have the following unidirectional one-to-many relationship: @PersistenceCapable public class Recipe implements