----- Original Message ----- From: "Jesse D. Sightler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 24, 2002 11:04 AM Subject: Re: Configuring a web service...
> Hi Steve, > > This is the best suggestion that I've seen so far, and is probably what > I will go with (although, I will probably just place the config file in > the WEB-INF directory of the web-app for now). WEB-INF/classes is good; you can load it as a resource. > > Thanks for all of the ideas. It would be nice if Apace Axis provided a > more standardized way of doing this, but it seems the config-file > approach is relatively "pure". > XML config files are purer. I actually have used a two level config setup in the past; a hostname config can point to a cluster config; off the cluster config comes all the settings shared by >1 box in a cluster, including log4J settings, security policies (who can call your endpoints), etc. It works provided that ops gave you all the right config info from the beginning. But if you do need to change a setting on a cluster, you need to edit every box in turn. Hence the plan to move LDAP/JNDI
