Reputation: 705
I am trying to debug a very simple HTML GWT module in Eclipse, but the breakpoint in my EntryPoint
class does not get hit! I have the following setup:
My module contains a simple HTML file with one EntryPoint
(It's a proverbial HelloWorld). The application starts normally when I do Run As Super Dev Mode or Debug As Super Dev Mode, and I see server's and client's URL's and ports with no errors. I can navigate to the application's HTML URL to see the simple Label, and even recompile and see the changes if I modify the EntryPoint
class which contains the Label.
I have set my argument's log level to DEBUG (see tons of loading various modules) and even check marked Debug As Configuration to stop at the main method. The thing is, when I run the application in Debug Super Dev Mode for the first time to start the core server, I can see the breakpoint stopping in DevMode
class' main()
method (not afterward though when I make changes to the EntryPoint
and recompile by refreshing the browser). But when I set a breakpoint in my EntryPoint
's onModuleLoad()
, it gets ignored!
How can I get the server to put a hook on my EntryPoint
?
Upvotes: 0
Views: 271
Reputation: 3832
In some cases there is no code available for a JavaScript statement.
Try to use:
GWT.debugger();
which will always stops if you are using a debugger.
Upvotes: 0