Wednesday, May 3, 2017

Re: java.util.Lists in Gwt super dev mode debugger

Indeed, this seemed to have been an Intellij issue.  After upgrading to 2017.1.2, I can now see the contents of the list:



Thanks to Kirill and Thomas for leading me to the solution.

The connection between Intellij and Chrome is definitely squirrelly though.  I often have to execute the code server bookmarklet twice to finally get Intellij to stop at a breakpoint and sometimes Intellij won't reconnect to Chrome until I close and restart it. 

OTOH, debugging directly in Chrome is more dependable but much less user friendly.


On Tuesday, May 2, 2017 at 11:02:08 AM UTC-4, bclark wrote:

We recently decided to integrate Material Design into our mature GWT application and this has finally forced our hand on moving from Legacy dev Mode to Super dev mode. We have this working fairly well using Chrome and Intellij IDE, 2016.2. One lingering problem though is viewing Java containers (Lists, Maps, etc.) in the debugger. In the screenshot below, the two expanded supportingCopyWidgetPresenters and supportingCopyEventPageBlockContentElements are both declared as java.util.Lists:


In case this is hard to read, the debugger is showing both lists values to be:

array = Internal error: com.google.gson.JsonParseException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at line 1 column 1386

Is there a special argument I need to pass to super dev mode to have it interpret Lists (and Maps, for that matter) correctly in the debugger? Is this a matter of telling super dev mode to use a different JSON parser?


Any help is greatly appreciated!


Note: This is cross posted in stackoverflow here:

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