Hi Maxime,
The web.xml used by the embedded Jetty should respect the standard servlet
specification. In other words, you should be able to define your servlet and
have it configured in the embedded Jetty server during hosted mode
debugging.

A couple of questions to help you get your servlet working with the embedded
Jetty server:

1) I noticed that you placed the web.xml file in a directory called
WEB-INFO/web.xml. According to the Servlet 2.5 API specification, the
directory structure requires the WEB-INF folder to be named as such (i.e.
the WEB-INFO in your example needs to be corrected). Could you double-check
that it is indeed WEB-INF, and if not, try switching it to see if that
solves the problem?

2) Could you clarify a bit about what error message you are seeing or how
Jetty is failing to load your servlet (provided that you use the correct
WEB-INF directory structure)?

3) What's being used in your custom servlet? Are you using any server-side
technologies or frameworks, or logging mechanisms? These can also cause
issues when you reach the part of your development phase where your
server-side starting building out a bit more (in which case you would use
hosted mode with your own custom server instead of the embedded Jetty by
using the -noserver option).

Hope that helps,
-Sumit Chandel

On Sat, Jun 6, 2009 at 5:44 AM, mabead <[email protected]> wrote:

>
> Hi,
>
> I was previously using GWT 1.5.3 and I tried to migrate to GWT 1.6.4.
> In my module configuration file (module.gwt.xml), I configure GWT to
> load one of my servlets that extends HttpServlet (and not
> RemoteServiceServlet).  This is the tag that I added in my gwt.xml
> file:
>
> <servlet path="RESTProxy" class="com.foo.bar.server.RESTProxy" />
>
> According to
> http://code.google.com/intl/fr/webtoolkit/doc/1.6/DevGuideOrganizingProjects.html#DevGuideModuleXml
> :
> "NOTE: as of GWT 1.6, this tag does no longer loads servlets in hosted
> mode, instead you must configure a WEB-INF/web.xml in your war
> directory to load any servlets needed."
>
> I tried to move my definition to WEB-INFO/web.xml but it looks like
> the new jetty browser only supports servlets that extend
> RemoteServiceServlet instead of HttpServlet.  At least, all the
> examples that I looked at gave me the impression that jetty does not
> support HttpServlet.
>
> Can anyone please confirm that Jetty supports plain HttpServlet?  If
> it does, can anyone provide an example?
>
> If it doesn't, is there any way to use the legacy tomcat browser with
> GWT 1.6.4?
>
> Regards,
> Maxime
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to