Re: Datastor issues - persistent POJOs

2010-10-09 Thread Will
Thanks again Didier for all the replies Apologies for dragging the issue out... another query (no pun intended! :-)) 1. I noticed I can avoid cloning POJOS on client and server if I place my POJO in /shared and use an encoded string as the key and not the Google Key... e.g. @PrimaryKey @

Re: Datastor issues - persistent POJOs

2010-10-08 Thread Didier DURAND
Hi Will, I developped some mechanism based on reflection API to qutomatically do gets from Objectfiy pojo and sets to client pojo when going from server to client and gets from client pojo to sets of server pojo when going from client to server. This avoids me typing all this code and making err

Re: Datastor issues - persistent POJOs

2010-10-08 Thread Will
Hi Guys, [i had started with cloning client/server types so i think i'll try and get this version working before refactoring to use objectify] I was just wondering (Didier), when retrieving from datastores, how do you normally deal with casting/converting your returned datastore objects to the cl

Re: Datastor issues - persistent POJOs

2010-10-08 Thread William Shatner
Many thanks for the replies lads... On Fri, Oct 8, 2010 at 18:17, David Chandler (Google) < drfibona...@google.com> wrote: > Have a look at GILEAD for JPA / JDO on App Engine: > http://turbomanage.wordpress.com/2009/10/15/gwt-gae-and-the-balm-of-gilead/ > > Also, Objectify-appengine provides emul

Re: Datastor issues - persistent POJOs

2010-10-08 Thread David Chandler (Google)
Have a look at GILEAD for JPA / JDO on App Engine: http://turbomanage.wordpress.com/2009/10/15/gwt-gae-and-the-balm-of-gilead/ Also, Objectify-appengine provides emulation for Key and related classes so that POJOs can be used with GWT. http://code.google.com/p/objectify-appengine/ HTH, -- David C

Re: Datastor issues - persistent POJOs

2010-10-07 Thread Didier DURAND
I personally use the clone technique: i.e a simple pojo with no annotation. You may later on face a second issue with your annotated objects if their methods use server side specific objects or methods: the emulated part of JRE in gwt is fairly small: see doc. so, separating client and server sid

Datastor issues - persistent POJOs

2010-10-07 Thread Will
Hi, I'm constructing a POJO (Employee) on teh client side and trying to make persistent in teh datastore. So that both client and sever can see this class i place it in the / shared folder and annotate the object as suggested by tutorials for persistence... @PersistenceCapable public class Employ