Cannot Debug GWT with Eclipse

2016-10-16 Thread Namline
Hi, 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: GWT version: 2.7 Eclipse version: Mars 4.5.2 Chrome version: 53 Running mode: Super Dev Mode (debug) My module contains a simple HTML file

Re: Cannot Debug GWT with Eclipse

2016-10-16 Thread zakaria amine
are you using Eclipse breakpoints? I think you have to use GWT.*debugger *() method. Le dimanche 16 octobre 2016 19:10:55 UTC+2, Namline a écrit : > > Hi, > > I am trying to debug a very simple HTML GW

Re: Cannot Debug GWT with Eclipse

2016-10-16 Thread Jens
SuperDevMode compiles your Java source transparently to JavaScript, it never executes your Java source code directly in a JVM. So Java break points in your GWT app will never work. That means with SuperDevMode you can only debug your code using the browser, as thats the one who actually execute

Re: Cannot Debug GWT with Eclipse

2016-10-16 Thread Namline
Zakaria, I'm not following your suggestion here. What does a call to that particular method have to do with being able to set a breakpoint in Eclipse debugging (Super Dev Mode) to walk through the GWT application? (http://www.gwtproject.org/doc/latest/tutorial/debug.html) What I am seeing is t

Re: Cannot Debug GWT with Eclipse

2016-10-16 Thread Namline
Jens, I don't know why this user group requires approval to post comments, but I think in my reply to Zakaria, I mentioned that I was able to invoke Eclipse debugging if there is a server side code, e.g. RemoteServiceServlet (and that's what I was seeing). But you are right; the client side do

Re: Cannot Debug GWT with Eclipse

2016-10-16 Thread Namline
Jens, Actually, I took your advice and managed to set break points in Chrome's Developer tool (in Source tab, under sourcemap folder where the Java classes are) and debug from there (not that anything made sense with all the generated JavaScripts). I also tried SDBG which more or less does the