> Why not just give the MyProjectWeb project to the GWTShell in the > classpath? Provided you used the "client" and "server" subpackages of > the same "root" package in all three projects (or made a gwt module in > the same package as the server code in the MyProjectGwt project and > inherited it appropriately), with the appropriate <servlet/> > declarations in your GWT module, the GWTShell should pick up your > servlets and it should "just work" without the need for a standalone > servlet container.
Some opensource frameworks (Spring, Hibernate, etc.) are used in server side. I have configuration in web.xml. That is why I prefer to use a standalone web server. Since I have a standalone server, I got to output compiled Javascript and RPC related files into web project with "-out" option. > Agreed (though sticking to the recommended client and server, and > possibly shared, subpackages, it's still fairly easy to *not* > reference client code form server code and vice versa). Human beings will make mistake if they are able to. I don't want to keep telling my developers all these rules and tricks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
