Re: Run GWT/GXT in Debug Mode while Deployed on WebSphere

Jens,

Thanks for the feedback. It certainly worked in Chrome (55). Unfortunately, I cannot use Chrome as the pages that I will be ultimately debugging run *drum roll* applets, so I have to stick with IE. Is there a way to get SDBG to work with IE and GWT Eclipse Plugin?

On Thursday, February 2, 2017 at 4:47:37 AM UTC-5, Jens wrote:

However, when I place the breakpoints in that simple application, it only catches breakpoints on the RPC service side of the application, and no breakpoint is caught on the GWT side, e.g. on any of the registered handlers.

SuperDevMode (SDM) compiles everything to JavaScript and the browser executes it. So generally you need to set break points in your browser dev tools as the code is executed by the browser. However the GWT Eclipse plugin should install the plugin "SDBG" as well, which allows Eclipse to connect to Chrome Dev Tools and then you can set break points for JavaScript in your IDE instead in the browser. To make that work the plugin needs SourceMaps generated by SDM which contain information about the Java <-> JS mapping.

So you should check:

- Is the SDBG plugin installed

- Can Chrome Dev Tools access SourceMaps (Do you see Java files in the sources tab of Chrome Dev Tools)

- Does Eclipse connect to Chrome

Hope that helps. Personally I use IntelliJ and set break points directly in the browser, so I can't really give you any further help. But the above should give you an idea about what might be wrong in your setup.

-- J.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.