Thursday, April 23, 2015

Re: SDM and client debugging with eclipse debugger?

Good news! I got it working now with the sdbg plugin - after restarting everything (eclipse, jboss, debug configs, sdm on) , the debugger pauses in the client code at the break points set :-)

On Thursday, April 23, 2015 at 12:13:04 PM UTC+2, wrote:
Hi Ivan, 

in the meantime I was able to install the sdbg plugin and tried to use it according to video from the github readme page of the project. 

Difference was that I did start Codeserver via  Debug -> [GWT] Web Application (Super Dev Mode) and did not get a classnotfoundexception for the CodeServer. Also - since I have to use the target app server as runtime environment (e.g. JNDI-Lookup), I did provide the URL of the local JBOSS when creating a "Launch Chrome" Debug Configuration instead of the URL from the Development Mode View in Eclipse. 

Unfortunately I do get the same behaviour that the debugger does not halt at the break points in the client code. Should it work as expected also with local jboss as runtime instead of GWT-Plugin-internal JETTY Runtime?


On Thursday, April 23, 2015 at 9:10:01 AM UTC+2, wrote:
OK, thanks for the info! This clarifies the behaviour I described in my initial post.

On Wednesday, April 22, 2015 at 3:23:32 PM UTC+2, Jens wrote:
With SDM your client side code only runs in the browser and you have to set break points in the browser's dev tools. Launching the JVM in debug mode does not give you anything for client side debugging.

There is an Eclipse plugin called SDGB on Github that allows Eclipse to connect to Chrome browser and then you can set break points in Eclipse (and Eclipse synchronizes them with Chrome browser).

-- 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