Craig R. McClanahan wrote:

> Many app servers have private deployment descriptors for "extra"
> information, similar to what Remy is proposing -- indeed, one could claim
> that Tomcat does this already with how we use $CATALINA_HOME/conf/web.xml
> to set default behavior (well, at least until Costin's recent patch :-).

Not sure what patch you're talking about, it should still work.
I only added code to deal with the case when the default web.xml is not 
found ( i.e. no defaults - all config in the app WEB-INF/web.xml ).


> * IMHO, the deployment descriptor should be viewed as an
>   output of a development process, rather than an input --
>   just as you package .class files (created from .java files)
>   for all your bean classes.  It is straightforward to create
>   an Ant build.xml file (or whatever) that assembles fragments
>   provided by the application developer, plus fragments generated
>   by JSPC, into the ultimate web.xml file packaged in the webapp.
>   The developer should never even have to look at the
>   merged version of this file (in the same way that developers
>   using an IDE-type tool that auto-generates web.xml files
>   avoids the need to look at it).

+1 - except that I'm not sure we use the same vocabulary :-)
The .WAR and WEB-INF/web.xml are the output of the development process,
shiped to the deployer. 

"Deployment descriptor" should be part of the deployment process - 
that includes TOMCAT/webapps/myapp.xml and any other deployment files
we may generate or use as part of the deployment. Web.xml is a "deployment
descriptor" too - and is one input in the deployment process. 

Many servlet containers use a WEB-INF/CONTAINER.xml deployment descriptor,
part of the .WAR. IMHO that's a very bad practice - it allows the .war to
control the URL or other properties, and this may affect the security in 
some cases.  

In tomcat5 - I think we should reduce the use of tomcat-specific deployment
and config files, we already have JMX that abstracts the config, and we
should try to be consistent ( i.e. use some generic JMX config file ).

Costin






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to