That's how we did it originally, but then we created a separate GWT project (well, actually it's just a JAR project) that defines all our types that are common over the RPC interfaces. We reference that project in both the server and client projects, and the JAR gets pulled into the client side and GWT happily generates JS code from it. We now also use it for some 'shared' client-side classes as well so it's effectively just a library project.
DaveS. On Nov 9, 3:35 am, rjcarr <rjc...@gmail.com> wrote: > Hi Sanjith- > > I don't completely follow your question but any shared code between > the client and the server has to reside in the client package (by > default). This is because GWT can only see code in the modules you > have defined and the server package isn't a GWT module (again, by > default). > > Hope this helps! > > On Nov 8, 10:30 am, Sanjith Chungath <csanj...@gmail.com> wrote: > > > Greetings to all, > > I have defined a class in the server and want to get a list of > > objects (of that class) as return parameter of an async call. But while > > compile I got following error "No source code is available for type > > com.abc.pqr.data.XXX; did you forget to inherit a required module?". I know > > that it is because GWT dont know the java script code for coresponding > > class. What is the general practice to use a object of class in server side > > at client code, serialize it? or any other better way. > > > -Sanjith. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
