Wednesday, January 22, 2014

Re: 2.6.0-rc3 and Jetty's WebAppContext (jetty-web.xml)

or using -noserver and losing the Eclipse debugger

You don't loose Eclipse debugger when using -noserver. Just launch your app server of choice with debug enabled and then connect to it with Eclipse. You can also configure Eclipse to launch a Jetty of your choice (or any other supported app server) and let Eclipse deploy your application automatically to that Jetty instance (Eclipse WTP)

Personally I pretty much always use -noserver just because I want to use the same app server during development as for production. I don't think I loose anything (development speed, debugging, hot re-deploy) compared to using the build in Jetty of GWT.

-- J.

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment