How do I use my own server in hosted mode instead of GWTs built-in Jetty instance?
If you do not need to use, or prefer not to use, the Jetty instance embedded in GWT’s hosted mode to serve up your servlets for debugging, you can use the -noserver flag to prevent Jetty from starting, while still taking advantage of hosted mode for debugging your GWT client code. If you need the -noserver option, it is likely because your server-side code that handles your XMLHTTPRequest data requests requires something more, or just something different than Jetty. Here are some example cases where you might need to use -noserver: • You need an EJB container, which the embedded Jetty server does not support. • You have an extensive Servlet configuration (with custom web.xml and possibly server.xml files) that is too inconvenient to use with the embedded Jetty. • You are not using J2EE on the server at all (for example, you might be using JSON with Python). When using the -noserver flag, your external server is used by the GWT Hosted Mode browser to serve up both your dynamic content,
If you do not need to use, or prefer not to use, the Jetty instance embedded in GWT’s hosted mode to serve up your servlets for debugging, you can use the -noserver flag to prevent Jetty from starting, while still taking advantage of hosted mode for debugging your GWT client code. If you need the -noserver option, it is likely because your server-side code that handles your XMLHTTPRequest data requests requires something more, or just something different than Jetty. Here are some example cases where you might need to use -noserver: • You need an EJB container, which the embedded Jetty server does not support. • You have an extensive Servlet configuration (with custom web.xml and possibly server.xml files) that is too inconvenient to use with the embedded Jetty. • You are not using J2EE on the server at all (for example, you might be using JSON with Python). When using the -noserver flag, your external server is used by the GWT Hosted Mode browser to serve up both your dynamic content,
