I'm trying to debug a GWT 2.3 front-end that talks to an existing REST-based back end. What I'd like to do is allow the back-end to serve the GWT files out directly using the GWT noserver flag, as that mimics the production configuration and eliminates cross-domain concerns. The existing code makes meaninful use of methods besides just GET, so cross-domain solutions would be more invasive to the back end.
Currently, I have created a run configuration with both "-noserver" and "-war /x/y/z/myLocation" parameters. The GWT plugin is already passing in its own -war parameter, but this 2nd one seems to override; it must be an absolute path, as it appears that the working directory is the parent directory of the default war location.
For the most part, this works, as changes are picked up immediately and logging is properly sent to the GWT debug panel. But, breakpoints are not honored, presumably because the GWT plugin doesn't know anything about my 2nd WAR location.
Is there a better way to accomplish this? I've also tried playing with symbolic links to the default GWT war location, as well as trying to include that path in my existing application. But, none of those work well. I'm about to break down and use Apache's mod_proxy to split the traffic out to my existing server and the standard GWT Jetty instance, but that seems like an overly complicated solution.
If there is no better way to accomplish this, any chance that we could get a war location option for GWT configurations? Ideally, it would be possible to specify this relative to the module or project roots, making it much easier to share run configurations. This would make it much easier to use the noserver GWT option the way it was designed.