Hi Greg, I think you mix up something. The separation of client/server-code (to decide which to compile to Javascript) has NOTHING to do with packages. The separation of client code has to do with modules (.xml).
You could easy use the same package for client and server code. Just use a sub project for server code with the same package. This does not mean I recommend to do so, but to state it would be impossible is just wrong. Stefan Bachert http://gwtworld.de On 23 Aug., 15:36, Greg Dougherty <[email protected]> wrote: > Stefan, > > You can put the *,shared package in both the client and the server. > You can't put any java code that won't compile under GWT in both. And > you should have no desire to put all your server code on the client, > or all your client code also on the server. No? > > IOW, there's a REASON why you have three separate packages: client, > server, and shared. NO? > > Greg > > On Aug 22, 4:06 am, Stefan Bachert <[email protected]> wrote: > > > > And, IIUC, you CAN'T put the client and server code in the same > > > package. > > > > Greg > > > Hi Greg, > > > shared code IS running on both sides. > > It it easier to separate when code is in different packages. > > > Stefan Bacherthttp://gwtworld.de -- 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.
