Hi Rob, Did you stop by the GWT office hours at I/O? If so, I probably saw you there :-)
Regarding the use of a default servlet - GWT 1.6 (and GWT trunk) have switched to using an embedded Jetty server instead of Tomcat. Therefore, if your default servlet config that used to work with the embedded Tomcat but no longer with the embedded Jetty server, I would recommend seeing if your default servlet is doing anything at a low enough level that could differ from container to container. The more general solution, however, is to use hosted mode with the -noserver option and your own development server. What's best about this approach is that by using your own development server, you can debug both your GWT code safe in the knowledge that what you're testing on the server-side will match as closely as possible the live environment on the production server. Instructions on running hosted mode with the -noserver option: http://code.google.com/webtoolkit/doc/1.6/FAQ_DebuggingAndCompiling.html#How_do_I_use_my_own_server_in_hosted_mode_instead_of_GWT's If the servlet you're using isn't doing anything really low-level and really should be working in the embedded Jetty instance, let us know how it's failing for you and we might be able to help figure out where things are going awry. Hope that helps, -Sumit Chandel On Tue, Jun 2, 2009 at 8:16 AM, Rob Heittman <[email protected]>wrote: > > Hi all. Good to see so many GWTers at I/O! > > I have a use case where I would like to supply my own default servlet > in Hosted Mode, to emulate the behavior of a default servlet (/) > attached in the production app. This serves various resources whose > URI paths I don't know at compile time to incorporate in my web.xml by > name. > > In 1.4 and 1.5, I could supply a catchall servlet (/*) that forwarded > to GWTShellServlet when the requests were in the module path, but in > recently moving to (2.0) trunk, this approach no longer works ... I > suspect it wouldn't work under 1.6 either, unless maybe I was in > legacy Tomcat mode. > > I like the hosted mode server behavior so much better in the new > model ... but the resource finding behavior of the default servlet > seems deeply wired in; I don't know if there is a simple way (or even > a painful way) to supply an alternate default servlet. Ideas? > > Thanks all, > > - R > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
