On May 31, 7:33 pm, Gambo <[email protected]> wrote: > Hi there, > > maybe there were some answers serveral times on this topic but I > couldnt find them. > > I am looking for a best practise of gwt project setup with java > backend. > > As usual we are setting up our database first and then doing the > object relation mapping afterwards, creating DTOs and client classes. > For now this is a very manual job and we have to do mapping each time > by hand in jpa. This costs a lot of time and its redundant work(db > design and then design it again in orm). -------------- I do not know whether this is the best practice. I suggest a new practice. DataStoreGwt, a persistence engine for GWT, seeks to get around the above problem - maintaining shadow model for database purpose.
J.Ganesan www.DataStoreGwt.com -------------- > > Is there a better way to do this via Spring or Seam automaticaly? > Sorry but now I am a little bit lost what options I could use. > > If this is the wrong group to ask please let me know. > > Thanks for your help -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
