SDM with modular-webapp - no client-side debugging possible

[Magnus]

Hi,

when running an app built with maven and the modular-webapp archetype in SDM, client-side debugging does not work.

I start SDM in two terminals like this:

mvn clean install -Dgwt.draftCompile

cd *-client && mvn gwt:run-codeserver -Ddev

 

mvn tomcat7:run -Ddev

Then I can open the app at http://localhost:8080. But in chrome's debug console, the source maps are not available. There is not section "localhost:9876".

I hoped that they would appear when recompiling from within chrome, but this also doesn't work:

When clicking "DevMode On" the standard menu appears: "Choose a module to recompile:", and it offers: "app: off".

When hovering "off" it says "Click to turn on without recompiling." When clicking on it, nothing happens.

When clicking on "Compile" nothing happens.

SDM works fine for me when I run the two processes from within eclipse.

What's wrong here?

Thanks

Magnus

[Magnus]

I have reproduced the following a dozen times:

• Begin with a new app based on modular-webapp archetype: works!
• Add my own gwt library:
• add dependency to the modular-webapp's client pom
• add inherits-statement to modular-webapp's client gwt module xml file
• add code from my library to modular-webapp's App class
• After that it stops working: Clicking on "Devmode On" and then "Compile" has no effect!
• When I remove all the stuff mentioned above, it does not work again after recompiling server and client.
  It seems that there is something cached somehow...

Any help is welcome!

Magnus

[Magnus]

Could please someone give a little feedback?

How could you further localize the problem?

For example, normally, when selecting "DevMode On", there is something going on in chrome's "network" tab: dev_mode_on.js is loaded and when you click on "compile" a lot of messages are written.

In my case, when selecting "DevMode On", dev_mode_on.js is loaded, but when clicking on "compile" there is no further message in the "network" tab.

Can you further debug this?

Meanwhile, it all depends on single line of code: If I comment it out, SDM works. If I uncomment it, SDM does not work.

Please point me to the right direction...

Magnus

[Magnus]

I see, I am on my own with this issue...

Nevertheless, I post my proceedings here. Maybe it helps someone someday...

Well: There must be some side effect between the SDM dialog box (div) which shows "Choose a module to recompile" and my library test code.

My library test code also is a DialogBox, i. e. a class "TestBox extends DialogBox", and located within my library. To test if my library works within my modular-webapp project, I created an instance of TestBox.

The current observation is this: As long as the instance of TestBox is visible, clicking on "compile" in the DevMode On box will have no effect.

As soon as it is hidden, SDM compile will work again.

So I believe (hope) that this behavior does not have to do with my specific maven or java configuration. Since there is not a real need to recompile when a dialog box is open, I think (hope) that I can live with this issue.

Magnus

[Thomas Broyer]

Inspect the DOM, you might have a transparent element layered on top of the SDM dialog (and have a look at the zIndex for each; the SDM dialog uses a very high zIndex but maybe you're using one even higher?)

[Thomas Broyer]

BTW, how about using <launcherDir> to have "recompile on load" instead of using the bookmarklets?

[Kay Pac]

I'm not sure I understand how launcherDir would allow you to recompile on load? Doesn't this just set an output directory?

[Thomas Broyer]

…where SDM will write a .nocache.js file that compiles on load. This is how DevMode calls SDM under the hood.