Wednesday, January 22, 2014

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

Thanks, Jens. It's almost coming together, but not quite.

I've got Tomcat started with debug and I've got Eclipse linked to it (per However when I make a change to my servlet, I don't see it reflected in the run. 

I've got the Eclipse Web Application DevMode -noserver option and -war /Library/Tomcat/catalina/webapps/myapp
I changed a line of debug in my servlet and ran this. The servlet's class file does not change, and the new log message does not appear. How do I make this work?

On Wednesday, January 22, 2014 4:25:43 PM UTC-5, Jens wrote:
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