Re: Cannot Debug GWT with Eclipse

There are only two arguments needed to run GWT Development Mode (a.k.a Super Dev Mode.) If you're using the new GWT Eclipse Plugin V3, use the GWT Development Mode to start up the Super Dev Mode CodeServer. The arguments will be -launcherDir path/to/WAS/webapp/dir and gwt module. Then, you'll noti

Re: Cannot Debug GWT with Eclipse

My setting is straightforward although I have to say this is simply for me to start learning about debugging GWT, and more so, doing it on an external server (so I don't have much restrictions). I am running WebSphere Application Server (8.5.5) and have my GWT application deployed (war) which I

Re: Cannot Debug GWT with Eclipse

Thanks for the pointer. >From the cited github thread I didn't understand If you deprecate bookmarklets will I be able with the new scheme to? 1) debug cors enabled GWT widget in the production site? 2) will it work with different OS/browsers combinations from my development PC (my RDP setup). O

Re: Cannot Debug GWT with Eclipse

On Thursday, October 20, 2016 at 10:39:34 AM UTC+2, Vassilis Virvilis wrote: > > Hi, > > Are we talking about debugging using SDBG plugin, setting breakpoints from > the IDE +that kind of thing? > > Because if you don't you don't need any reverse proxies for http. I am > using it all the time a

Re: Cannot Debug GWT with Eclipse

Hi, Are we talking about debugging using SDBG plugin, setting breakpoints from the IDE +that kind of thing? Because if you don't you don't need any reverse proxies for http. I am using it all the time and development machine where the codeserver runs is different from the production server. I am

Re: Cannot Debug GWT with Eclipse

> Is there a way to debug the GWT application (client and server) just like > your plugin allows while running in SuperDevMod while it has been deployed > on an application server, e.g. WebSphere with say, localhost:9080/MyApp > context root? > As long as the Application server runs on the sa

Re: Cannot Debug GWT with Eclipse

Sure you can debug on any server, that said, if the web server is on a different ip than the code server there's an issue to workaround, b/c the project.nocache.js has hostname issue. I'm not sure if this is the case for you yet, but usually when you want to debug on a different server they have

Re: Cannot Debug GWT with Eclipse

Is there a way to debug the GWT application (client and server) just like your plugin allows while running in SuperDevMod while it has been deployed on an application server, e.g. WebSphere with say, localhost:9080/MyApp context root? On Tuesday, October 18, 2016 at 11:51:22 PM UTC-4, Brandon

Re: Cannot Debug GWT with Eclipse

Thanks for the update. Sounds like some of the name space had to be reset in the configuration. I've seen this happen until the project is refreshed or reimported. On Tue, Oct 18, 2016 at 7:00 PM Namline wrote: > Brandon, > > Sorry for the delay in response (happy hours). So, here's what happene

Re: Cannot Debug GWT with Eclipse

Brandon, Sorry for the delay in response (happy hours). So, here's what happened (I am running Eclipse Mars 4.5.2 (R2) with Google Plugin for Eclipse already installed (Windows 7)): I installed GWT Eclipse Plugin 3.0.0 from Eclipse market place, and as you had suggested, on the second page, I

Re: Cannot Debug GWT with Eclipse

Good question. The goal is to uninstall GPE or GPE-Fork. I put in a conflict so it will ask you to uninstall it. I recommend using Java EE Neon and starting with a clean install. I haven't tested enough of the uninstalling. In theory it should work fine. I did find some hiccups along the way, but I

Re: Cannot Debug GWT with Eclipse

Brandon, Thanks. I just watched your video on YouTube. Excellent job for newbies like me. Quick question. As a starter, I have Google Plugin for Eclipse installed. Do I have to uninstall it before installing GWT Eclipse Plugin V3? On Monday, October 17, 2016 at 1:40:43 PM UTC-4, Brandon Donne

Re: Cannot Debug GWT with Eclipse

SDBG is the way to go for debugging, like they said. Keep in mind if the Chrome dev tools are open it will take over the breakpoints, and they are stated in Chrome dev tools. If Chrome dev tools are closed, and you opened debugging the browser with the SDBG Javascript debugger shortcut, then E

Re: Cannot Debug GWT with Eclipse

Maybe try out the new GWT Eclipse Plugin, which (AFAICT) bundles everything together: http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/debugging/Debugging.html On Monday, October 17, 2016 at 12:48:38 AM UTC+2, Namline wrote: > > Jens, > > Actually, I took your advice and managed to

Re: Cannot Debug GWT with Eclipse

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

Re: Cannot Debug GWT with Eclipse

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

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

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

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