Just a little note - once you use the source tag: <source path="XXXXX"/> in youe .gwt.xml, where XXXXX is different than client (the default package), you'll have to specify <source path="client"/> if you still want to client package to be searched for source files.
On 5 out, 05:53, Paul Robinson <[EMAIL PROTECTED]> wrote: > You don't need client & server code in the same jar - just on the classpath. > The source code also needs to be on the classpath, as do the .gwt.xml files. > You can specify additional .gwt.xml files by importing modules in your > .gwt.xml file. > > In any .gwt.xml file, if you don't specify a source path, then GWT > assumes the equivalent of an entry of: > <source path="client"/> > This is relative to the place where you put your .gwt.xml file, and you > can have multiple <source> entries if you want. > > Code that is not intended for the client should not be specified here, > because specifying it will make GWT translate it to javascipt. Client > code can only reference javascript-translatable code...so you can't just > have your client reference any old java you have. > > HTH > Paul > > Justin Thomas wrote: > > I have to source how do you let it know where the source is? Does it > > have to be specified in the .gwt.xml file? I have tried that too. > > Where does the module go in the jar? Do the client/server code need > > to be in the same jar? I don't have it setup like that right now. > > > On Oct 4, 5:33 pm, "Ian Bambury" <[EMAIL PROTECTED]> wrote: > > >> GWT needs the source to compile and a module file in the jar > > >> Ian > > >>http://examples.roughian.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
