I don't think so.--
Typically you would use some sort of a config file per environment (e.g. testing, production, development) and then simply switch config files.
On server side you would bundle the correct config file into the *.war file and on client side you could use GWT's Constants mechanism.
If you use Maven then Maven's resource filtering + different Maven profiles can be used to produce different config files based on the active Maven profile.
In my non-maven project I have three config files: dev.properties, prod.properties and app.properties. The app.properties will be bundled into the *.war file and my ant script makes sure to overwrite the app.properties with one of the other two files depending on an environment property that I provide during the ant build.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
Post a Comment