Howdy,
>But that's the way I want it to be. At the moment my apps are machine
>dependant because they use the
>web-inf/web.xml file but if I could use the server's web.xml file
instead I
>would not have to reconfigure every time I move an app across to my
live
>server.
Nearly all non-trivial web applications have environment-specific
settings. There are many standards-compliant, portable ways to deal
with this. For example, you can have tokens in your web.xml and have
ant fill them in depending upon the environment you're deploying to. Or
you can have <Enviroment> entries in server.xml with the <env-entry>
references in web.xml. Either of these is far superior to putting
anything in a container-specific location not intended for use in the
way you want it to.
If you still think it's a good idea, you can maybe do this by converting
the parameters from servlet init params to context params, and putting
those in conf/web.xml, e.g.
<context-param>
<param-name>myParam</param-name>
<param-value>myValue</param-value>
</context-param>
They will then be accessible via
getServletContext().getInitParameter("myParam"); in your servlets.
Yoav Shapira
Millennium ChemInformatics
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom it is addressed, and may not be
saved, copied, printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
