Thanks all for the feedback. I guess I will start with having a good look at Objectify.
Other question:is there any open source project that you guys know of which fully generates a gui dynamically in GWT based on introspection of the objects? Based on this info a basic GUI with List, Detail, Create, Modify functionality could be generated (not code generated to be clear, dynamic generated GUI). Of course this approach will not do for all requirements but it could be usefull for some administrations screens. BR On 26 jan, 08:36, Didier Durand <durand.did...@gmail.com> wrote: > Hi Jonas, > > Yes, moving to Objectify is definitely a good move: especially since > the GAE google team pushes toward 3rd party package rather than > datanucleus impl of JDO/JPA currently used by GAE. > > But, it doesn't sometimes prevent the need of DTO: if, for example (my > own cas), you want all your back-end objects implemented with > Objectify to inherit from an hierarchy of core objects delivering > services to application objects via inheritance, you willat some point > use DTOs because the high-level of the hierarchy have to be transcoded > to js via GWT compiler and the may use JRE classes and methods not > supported by GWT compiler. > > So, using Objectify is right but may not prove sufficient in all > cases. > > regards > didier > > On Jan 26, 8:18 am, Jonas Gehring <gehr...@egotec.com> wrote: > > > > > > > > > hi, > > > take a look at the persistance framework > > "Objectify"http://code.google.com/p/objectify-appengine/ > > > Objectify entities can be used in GWT without the need for Data > > Transfer Objects. > > > On 25 Jan., 21:52, GeneralSlaine <lennart.ben...@gmail.com> wrote: > > > > Hi all, > > > I've been having some issues with getting my persistant object to GWT > > > web front-end for example when implementing a web page to modify this > > > object. Ideally I would like to be able to reuse the same class both > > > for back-end as for front-end. > > > So far, I have not managed. > > > Instead I have a backbone class: Product and a front-end class > > > FProduct. Communication between front-end and backbone is always via > > > FProduct. So, when moving an object from backbone to web fornt, I have > > > some sort of helper class to create an FProduct out of the real > > > Product object. > > > > Major disavantage is of course the back and forward copying and all > > > the code associated with this. > > > > Do you guys have better approaches? I'd love to hear your ideas/ best > > > practises. > > > > BR -- 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-java@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.
