Tuesday, January 9, 2018

Re: Debugging GWT Client side code

On Tuesday, January 9, 2018 at 8:06:26 AM UTC+1, Monika Yadav wrote:
Hi All,

I am trying to debug the GWT client code while redirecting from a FreeMarker screen to a GWT screen. I am not able to do this using eclipse due to missing gwt.codesvr agrument while launching the GWT screen.
Please provide your inputs on this.

gwt.codesvr is for "extremely old" (or extremely big) projects still using the legacy devmode (superdevmode has been the default since GWT 2.7, released more than 3 years ago).
With superdevmode, there's no need for any URL tweaking any longer.
So, first, make sure you're using at least GWT 2.7 (or better, 2.8, which is more than a year old already, with 2.8.2 released a few months ago), then launch devmode as usual (make sure you/Eclipse don't pass "-nosuperdevmode" as argument).
Note that with superdevmode, debugging will happen in JS, with SourceMaps (i.e. in your browser dev tools, unless you happen to have a SourceMaps-compatible IDE; for Eclipse that would mean using the SDBG plugin)
See also http://www.gwtproject.org/articles/superdevmode.html#Debugging

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.

No comments:

Post a Comment