Debugging client side

[dcheeky77]

Hello!

It might be a stupid quetsion, but:
I started a simple project in GWT, developed forms in package *.client.gui and debugged with no problems (I'm using Eclipse Juno and its Google plugin, and I'm in development mode), even the client code (the Java version, I mean). After one change I made on the GUI the "client" code was ignored by the debugger (actually ran, the results appeared, but it simply didn't stop on the breakpoints).
Thinking I made something wrong in the code I reverted to the previous "breakpoint-able" version, but since then I cannot debug my "client" code. I figure it might be some environemnt setting, but I really can't figure out what nor can I be more specific on the problem :|
Does any of you have an idea of waht that might be?

Thank you very much in advance!

BTW: The server code stops correctly at breakpoints

[dcheeky77]

Something which might be connected: is it normal that for each change I make to the code I need to compile again everything? Now the whole recompilation takes 40 seconds, so it's becoming a bit of nuisance... :|
If I don't recompile, changes are not seen, neither on the "server" code, nor on the "client"...

Any ideas?

Thank you in advance!

[Thomas Broyer]

On Wednesday, December 5, 2012 4:28:10 PM UTC+1, dcheeky77 wrote:

Something which might be connected: is it normal that for each change I make to the code I need to compile again everything? Now the whole recompilation takes 40 seconds, so it's becoming a bit of nuisance... :|
If I don't recompile, changes are not seen, neither on the "server" code, nor on the "client"...

Any ideas?

My guess is that you're actually running your app in "prod mode", i.e. the URL is missing the ?gwt.codesvr= bit to trigger DevMode.

As for server-side code, you have to click the "reload server" double-spinning-arrow button to have your server-side classes reloaded. If that doesn't do the trick, then maybe you just disabled "Project → Build Automatically" in Eclipse?

[dcheeky77]

Thank you very much: the gwt.codesvr was actually lost in one of the redirection used in the authentication process. I never even thought of it (thing is, just now I learn its purpose)!!!
Regarding compilation, I was aware of the double arrows, but they don't work if I don't recompile the code (in that case they're useless anyway).
In case others need it, I reduces the compile time  by specifying to compile just for Chrome/Safari, by adding in the module .gwt.xml the folloing tag:

<set-property name="user.agent" value="safari" />

[dcheeky77]

SILLY ME!!! The parameter was lost twice! Your solution works like a charm!!! Thank you very very much!!! :)