Thursday, October 20, 2016

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 and development machine where the codeserver runs is different from the production server. I am also not using the -launcherDir option.

If you use the bookmarklets then yes, that won't be an issue (you may have other issues due to limitations of the bookmarklets, but at least not that one; that's why bookmarklets aren't recommended since 2.7.0 was released).
What they're talking about here is the interaction of -launcherDir and serving it from another machine (pointing -launcherDir to an NFS share or similar); see the issue linked to by Brandon.

I'll try to build a "devserver" that would do the reverse-proxying *and* some "magic" (paths whitelisting) to serve files directly from the codeserver; so you'd launch it like the codeserver with an additional URL to reverse-proxy to (see https://github.com/gwtproject/gwt/issues/9437#issuecomment-250926589)
But in the mean time, refer to the above discussion.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment