Hi David, I haven't tried the same setup with Tomcat yet, but I expect it should be the same procedure: In the "Servers" view in Eclipse, select the server you deployed the EAR to. Right-click it and choose "Debug". This allows you to set breakpoints in your server side code.
To debug the client side code, you can additionally start your GWT code server (the one that's usually on port 9997) in Debug mode (Select your GWT project, then "Debug As... > Web Application"). You should actually modify that debug configuration to uncheck the checkbox "Run built-in server"! (Because you're using Tomcat instead of the built-in Jetty). Now you'll only start the code server, without Jetty. Then, if you're using default values for your ports, you can browse your application with something like: http://127.0.0.1:8080/MyProject.html?gwt.codesvr=127.0.0.1:9997 (instead of http://127.0.0.1:8888/MyProject.html?gwt.codesvr=127.0.0.1:9997) HTH Chris PS I'd really be interested, if it works with Tomcat, too - please report back. On Mar 31, 8:14 am, David <[email protected]> wrote: > Cris, your notes were really helpfully. > > However I would like to know how you manage to debug your application > using your Glassfish (tomcat in my case) in order to use breakpoints > and those stuff. > > Thanks you so much -- 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.
