Hi Jacob, I think the decision about where the locally stored data should go should be done at build time. I'd suggest to use two directories within the ant tree structure:
/web/.... // stores the static data independent of location /web-production/ // stores the config data which should be used in production /web-preproduction/ // stores the config data which should be used in pre-production mode (testenvironment) /web-development // stores the config data which should be used in development context.xml could store the entry path of the locallay stored data /web-development/META-INF/context.xml // stores entry point and urls for development /web-preproduction/META-INF/context.xml // stores entry point and urls for pre-production /web-production/META-INF/context.xml // stores entry point and urls for production when I build I could say ant -Dtarget=production ant -Dtarget=preproduction ant -Dtarget=development and have the ant task copy the proper configuration files. This way I could easily test in preproduction and then deploy the same webapp, with only minor context configuration changes (and thus minimized error probability). What do you think about this approach? Johannes
