Pacane
Pacane

Reputation: 21471

GWT SuperDevMode breakpoints not working

I'm using IntelliJ, and I'm trying to put a breakpoint in a class, sometimes it works, but sometimes it brings the debugger in the file MyApp-0.js and I have to debug cryptic generated javascript.

Is there a way to navigate with my breakpoints in the corresponding Java file?

I am using IntelliJ 13.1.2

And yes, my GWT module uses the super dev mode settings:

<add-linker name="xsiframe"/>
<set-configuration-property name="devModeRedirectEnabled" value="true"/>

edit:

Also yes, I'm using the Jetbrains javascript debugging plugin in the latest version of Chrome.

I can access my sourcemaps from my code server manually by going to the code server page... Using IntelliJ plugin I go to http://localhost:9876/sourcemaps/MyApp/ and I see the source.

It'd be useful to see how the config should look like in IntelliJ maybe.

Upvotes: 13

Views: 6433

Answers (3)

Vadim
Vadim

Reputation: 1178

One of the most important differences between DevMode and Super DevMode is the environment that executes your code. JVM executes your GWT module in DevMode so the IDE can debug it like an usual Java application. The bad news about Super DevMode is that Chrome executes your GWT module, so the IDE does not know about breakpoints that you set in Chrome Dev Tools. If your breakpoints in Chrome Dev Tools don't work properly, I think this is a bug that should be reported.

Upvotes: 3

user3241019
user3241019

Reputation: 811

Try File -> Invalidate Caches and Restart.

Upvotes: 2

Martijn Wijns
Martijn Wijns

Reputation: 499

What are you using as your application server? You might have to specify the code server port somewhere in the application servers parameters as well.

Upvotes: 3

Related Questions