Sorry, maybe _I_ should be more explicit. In reference to updating the documentation, I meant including the need to create a web.xml file and package the server-side code into the webapp pathing. Parsing the module.gwt.xml file for <servlet> elements and inserting transformed <servlet-class> and <servlet-mapping> elements into an external web.xml, as well as automating the app-specific server-side packaging, should be relatively straightforward. It is the *need* to do those things that is not explicit. (Caveat: It is perhaps painfully obvious to others. I'm not exactly an experienced web developer, which is why GWT is so attractive to me.)
On other subjects, the documentation provides the GWT-RPC way of doing things along with a general abstraction to assist those employing another request handling mechanism. It seems like the -noserver documentation should include GWT-RPC-specific server-side packaging steps for completeness-sake. "...all server-side requests will be served by your web or application server of choice" seems insufficient (though obvious now that I look back). Maybe 'seems' is the operative word here. External-server Hosted Mode toes the line between understandable and automagical. I guess I suckered myself into thinking that the -noserver option would still handle the server config for me. Who knows how I got this to work a year ago, and why I didn't document it for myself. I will take your advice and submit changes. Thank you once again. On Oct 14, 2:10 pm, "Isaac Truett" <[EMAIL PROTECTED]> wrote: > Having an automated build and deploy process is just a good idea. It saves > you from the tedium and risk of manually moving files around. I would just > as soon choose not to automate my builds as I would choose not to keep my > project in a versioned repository. > I image that the topic of build process isn't mentioned in GWT's > documentation because it really isn't pertinent. Your project should have a > build process regardless of whether or not you use GWT and the use of GWT > doesn't preclude any specific choice of build process. > > Contributions of all kinds from non-Google-employees are always welcome. If > there's something you think would be helpful to add to the documentation you > can post it here or open an issue in the issue tracker. > > On Tue, Oct 14, 2008 at 1:50 PM, Christopher Venning < > > [EMAIL PROTECTED]> wrote: > > > Will do. As an aside, does the Documentation need to be more explicit > > about this or am I the exception here? If so, I can submit a change, > > if documentation updates are something non-Google contributors are > > allowed. Any moderators listening? > > > Thank you again for your assistance. > > > On Oct 14, 1:34 pm, "Isaac Truett" <[EMAIL PROTECTED]> wrote: > > > You'll want to set yourself up with a proper build process. I suggest > > Ant. > > > It's simple, powerful, and there are a number of examples you can borrow > > > from this forum. Have your Ant script build a .war file and copy it to > > your > > > tomcat/webapps directory. Tomcat's default configuration is to > > automatically > > > deploy any .war it finds in webapps. No server restart required. > > > > On Tue, Oct 14, 2008 at 1:18 PM, Christopher Venning < > > > > [EMAIL PROTECTED]> wrote: > > > > > Thank you very much. > > > > > For posterity: I compiled the my.module.server package (with > > > > dependencies) and exported to %TOMCAT_HOME%/webapps/ServerTest/WEB-INF/ > > > > lib, where I also copied gwt-servlet.jar (a dependency) from > > > > GWT_HOME. I also created the WEB-INF/web.xml file with the servlet > > > > mapping. > > > > > Now, I understand the web.xml and dependencies need to be updated with > > > > service changes, but this method also means that changing server-side > > > > code requires a server restart (which embedded-serer Hosted Mode > > > > requires anyways) along with a newly-minted server-side code extract. > > > > Don't get me wrong, you're my new favorite person, I just want to make > > > > sure this is the best option. Am I correct? > > > > > On Oct 14, 1:01 pm, "Isaac Truett" <[EMAIL PROTECTED]> wrote: > > > > > You're use GWT RPC, which means you have a RemoteServiceServlet > > somewhere > > > > > that implements the server side of that RPC service. You need to > > compile > > > > > that servlet to a Java .class file and deploy it to your web server. > > You > > > > > also need a web.xml file to map request URLs to your servlet. > > > > > > On Tue, Oct 14, 2008 at 12:55 PM, Christopher Venning < > > > > > > [EMAIL PROTECTED]> wrote: > > > > > > > On Oct 14, 12:53 pm, "Isaac Truett" <[EMAIL PROTECTED]> wrote: > > > > > > > Did you deploy your compiled servlet? I don't see it listed in > > the > > > > stuff > > > > > > you > > > > > > > copied to tomcat/webapps/ServerTest. > > > > > > > What do you mean "compiled servlet"? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
