Chuck Hinson <chinson <at> gestalt-llc.com> writes: > As for using the application's context in web.xml - that's just plain ugly; everytime I deploy, I have to > unwrap my war so I can modify web.xml to change hostname and port info. (Deployment-specific config info > just shouldn't be in web.xml)
Chuck, fwiw, we also experienced the same dilemma re: web.xml and deployment specific config info. The solution we took was to override the web.xml context parameter in the Web Container configuration. We have done this for Tomcat and Jetty. There is even a flag in the web containers parameter that prohibits the web.xml to override it so you make sure the value always comes fro the web container (the web.xml parameter exists, then, mainly to document the parameters accepted by the web app) -- yuri
