Re: Debugging application on external server

2011-12-14 Thread Jaroslav Záruba
Do I have to recompile+republish my app with the -noserver parameter? My understanding is that this parameter is there only for the DevMode launch, but OTOH I find it hard to believe it is possible to debug GWT using production html+js. (Sounds just too good to be true. :) -- You received

Re: Debugging application on external server

2011-12-14 Thread Thomas Broyer
The *.nocache.js contains code that sniffs for the presence of the gwt.codesvr= in the query-string to trigger DevMode; it then loads the hosted.html (or hosted.js, depending on the linker) instead of the *.cache.html (or *.cache.js). The hosted.html then loads the browser DevMode pluging

Re: Debugging application on external server

2011-11-30 Thread Alexandre Ardhuin
Hi, To debug a remote server you have to : - start DevMode on your localhost, - connect to your remote server with the normal url - add gwt.codesvr=localhost:9997 parameter to the url where 9997 is the port on witch DevMode is listening As exemple if you have your app running on

Re: Debugging application on external server

2011-11-30 Thread Thomas Broyer
The code server should be the machine where you run the DevMode, so if you run your browser on the same machine as the DevMode, it should just be localhost (only if you run DevMode on a machine and the browser on another one, or in a virtual machine, then you'll use the name of the machine

Debugging application on external server

2011-11-29 Thread mariuszym
Hi! I'm new in GWT and I have annoying problem with GWT. I started develop existing project (GWT module + EJB module) and I can't begin to debug this. Application is working on server Glassfish 2.1 (external server - not on my localhost). I have ant script which deploying app on this server, but