Hi Jeff Stevens,
From your mail I understand that you would like to have separate set of
global application variables for separate environments such as dev, integ
and load. We are doing something like this. It may not be the correct
approach. Besides web.xml we are having our own Configuration file called
the VBConfig.cfg which is resident in the WEB-INF folder of the deployed
application. Then we have a startup servlet that loads this file as follows
:
String vbConfigPath = getServletContext().getRealPath("/") +
"/WEB-INF/VBConfig.cfg" ;
And then we do System.getProperties().load() from this path. This way we
have a separate VBConfig.cfg file for development, system testing and load
testing environments. I hope this is what you were looking for.
Thanks
Ajay Mahajan
Wipro Technologies
>>>>>>>
We are wondering if we can define global application varibles elsewhere than
in the web.xml file. Perhaps in local.properties or something. We would
like to be able to push everyting in our application directory from
integration, to staging, to production without modification. We could then
use local.properties, or some other static file to set certian aplication
variables that differ from integration, staging and production.
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
