Home/ Questions/Q 6581303
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T16:08:08+00:00

while developing GWT apps we ran into lots of problems with project configuration. Let

  • 0

while developing GWT apps we ran into lots of problems with project configuration. Let me explain… As usual in development, we have few environments for our application: local, demo, preview and live. Of course they are running on different machines, some are using SSL while others don’t. But most importantly – all of them have different URLs.

Now, in few places in our application we need specify some URLs. Usually we would use *.properties files stored on server, and tools like Spring taglibs and it’s <spring:message /> tag. But since GWT does not have such tools, we ended up in leaving hard coded URLs and performing code replacement on different SVN branches. As you can imagine – this is the worst possible scenario, causing us much problems.

So, my question is:
how one could build proper, flexible mechanism of storing config properties shared for both client and server side in GWT application. This properties have to be available for server-side handlers, client app (compiled JavaScript), UiBinder, other code running on server (workers, Spring, etc.).

The preferred way would be to avoid gwtc build if we change value of some property, but I guess it will be hard to achieve. So I will accept any reasonable alternative.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    How about using relative URI references (e.g. absolute paths, without scheme or authority; i.e. /path/to/foo instead of http://example.com/path/to/foo)?

    And in the few places where you absolutely need an URI (with scheme and authority), then use another property to store the “prefix” (e.g. http://example.com), and then concatenate with the above path.
    Those places where you need a full URI should all be on the server, which means you don’t have to recompile your GWT project when you change the “prefix”, so everything is only runtime configuration and you can deploy the same artifacts in all environments.

    That being said, if you ever need something configurable at runtime in GWT, then use a dynamic host page and JSNI (or a com.google.gwt.i18n.client.Dictionary); see http://code.google.com/webtoolkit/articles/dynamic_host_page.html

    • 0