Are there any advantages to using <env-entry> tags inside a web
application's web.xml file instead of just using plain old vanilla
init-params? The J2EE spec suggests that somehow the former approach
is more flexible and permits a deployer to configure environment
variables at deployment time without touching the web.xml file. As
far as I can see, however, a deployer has to manipulate the web.xml
file to change env-entry values. Am I missing something?
Thanks in advance.
James Lawless - 05 Jun 2004 21:06 GMT
Hi,
AFAIK most containers will allow you to edit env-entries through the console
at runtime. This is done as the env entries are items in the containters
JNDI tree. This would negate the need to modify web.xml and rebuild.
However in my experience you often have to manually change the entries in
file to ensure the chnages persist beyond server reboots.
James
> Are there any advantages to using <env-entry> tags inside a web
> application's web.xml file instead of just using plain old vanilla
[quoted text clipped - 5 lines]
>
> Thanks in advance.