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 simpler, very efficient. My only was of accessing the datastore as of now. About JDO: future seems not so bright. Read section by Ikai Lan in this thread: http://groups.google.com/group/google-appengine-java/browse_thread/thread/defc6d14445318b8/75a1e7b5bcbc1bb3?pli=1 regards didier On 29 déc, 13:12, Kalyan Akella <kalyan.ake...@gmail.com> wrote: > 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 > here<http://code.google.com/appengine/docs/java/tools/localunittesting.htm...> > . > > Do you think there's a better alternative to doing testing than this way ? > > Sincere Regards, > Kalyan Akella -- 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-j...@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.
