rename-to module attribute and DevMode

[Joseph Lust]

We've been working with rename-to so that our apps (many submodules) don't all have ugly, huge urls with the full package name in them. This is working well, however when we switch to DevMode, it won't run. DevMode appears highly dependent on guessing the location of the X.gwt.xml file based on the URL. 

There was a gwt bug reported 3 years ago, which has not response to recent pleas, so I've had to just remove the rename-to attribute while debugging, which seems silly.

So how do others keep using DevMode with rename to as the GWT SDK appears unable to resolve the modules/gwt.xml in this case. Thanks for any pointers.

Sincerely,

Joseph

[Hilco Wijbenga]

On 24 September 2012 12:59, Joseph Lust <lifeo...@gmail.com> wrote:
> We've been working with rename-to so that our apps (many submodules) don't
> all have ugly, huge urls with the full package name in them. This is working
> well, however when we switch to DevMode, it won't run. DevMode appears
> highly dependent on guessing the location of the X.gwt.xml file based on the
> URL.

We have a very similar setup. We have never had any problems with
running in DevMode, though. Just run "mvn gwt:run". :-)

> There was a gwt bug reported 3 years ago, which has not response to recent
> pleas, so I've had to just remove the rename-to attribute while debugging,
> which seems silly.

Does that mean that you are trying to start DevMode from inside
Eclipse? We never do that so that might be the difference. It would at
least give you a place to start investigating.

[Joseph Lust]

Thanks Hilco,

We run via the RunAs>WebApplication option which uses the Eclipse GWT Plugin to run it. This throws various errors, though I don't have the output with me. It is to the extent of "cannot find X.gwt.xml on classpath." You can start grafting things onto the classpath, but I assumed the Google Plugin would be smart enough to work with it's own rename-to configuration. 

Also, we use DevMode in a remote (aka external) tomcat setup. We have the UI calls sent to the DevMode plugin, but the RPC's go to the running tomcat. That way we don't need to bring the whole system up and down to just mess with the UI (OSGi implementation of GWT/Spring backend with 30 subapps). However, this just won't jive using rename and the only option we see at the moment is to keep using the old/nasty long urls. :(

Thanks for any insights.

Sincerely,

Joseph

[Jens]

Hm we use DevMode and rename-to and never had any problems with it. We have something like App.gwt.xml, DevApp.gwt.xml (contains logging and inherits App.gwt.xml), DevAppGecko.gwt.xml (contains use.agent and inherits DevApp.gwt.xml) and all have the same rename-to="app" attribute, so we don't have to change the host html page script src path. We also run DevMode in Eclipse using the Google Eclipse Plugin and our server side code runs on an external server. So pretty much what you have.

In some few situations (like adding/removing modules in the run configuration) I remember that the command line parameters for DevMode were messed up by the Google Eclipse Plugin and you had to correct them manually. But that has happened quite some time ago and it never happened again since then. It's pretty much what has been said in comment 6 in your linked bug report I guess. Have you carefully checked the command line parameters for DevMode in your run configuration?

-- J.

[Thomas Broyer]

On Monday, September 24, 2012 9:59:00 PM UTC+2, Joseph Lust wrote:

We've been working with rename-to so that our apps (many submodules) don't all have ugly, huge urls with the full package name in them. This is working well, however when we switch to DevMode, it won't run. DevMode appears highly dependent on guessing the location of the X.gwt.xml file based on the URL.

There's no guessing: you give DevMode the list of modules you want, and it then keeps the modules in a map keyed by their rename-to.

[Joseph Lust]

To update this one, it seems a bug in the GWT Eclipse plugin was getting me. I had several projects with GWT modules open. When making a new WebApplication launch config, setting the "Project:" to say Project A, "Main Class:" to DevMode, selecting module A in "GWT > Available Modules" and hitting Apply, the wizard autocompletes various properties with module B from Project B which I never touched. However, Project B/module B was a have preexisting WebApplication config, so it seems those are leaking in somehow.

So, just wanted to clarify that it was not in fact the rename-to that was causing the problem, but the GWT IDE Plugin auto-incorrecting values in the WebApplication run configuration.

Sincerely,

Joseph