I've experimented with creating a code generator to use reflection to generate client side DTOs along with utility classes to convert between the two. This way, I'm only maintaining the classes in one place and the rules that the actual server side classes have to follow are reduced from what GWT-RPC requires. I'm not completely sold on this idea, but it's working for me for now.
The code generator is very rough right now and in no shape for sharing, but I may spend some time cleaning it ip eventually. Would anyone else be interested in a tool like that? -Brian On Nov 16, 7:01 am, Ray <[email protected]> wrote: > Hello, > > I have my model classes inside an library on the server-side which I > want user for different applications (not only GWT) > > Copying my domain classes to the client side of the GWT-Client-App > doesn't seem to be very convienient, as I have to maintain the same > code in two different locations. > > Is there no way to include the library and GWT creates the client-side > java-script whith the model automatically? > > Thanks > Ray > > On 11 Nov., 20:58, Dominik Steiner <[email protected]> > wrote: > > > > > Sanjith, > > > you can move the model classes to anywhere under the client folder, > > the client/domain example is just what i use here with me. And then > > the server will reuse those classes on server side where he will read > > the jdo annotations. > > > Let me know if it works for you > > > Dominik -- 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=.
