Date: 2004-01-27T17:14:03 Editor: GregWilkins <[EMAIL PROTECTED]> Wiki: Apache Geronimo Wiki Page: Architecture/WebContainer URL: http://wiki.apache.org/geronimo/Architecture/WebContainer
no comment Change Log: ------------------------------------------------------------------------------ @@ -14,9 +14,8 @@ A webapplication in either EAR, WAR or unpacked format is deployed by standard geronimo mechanisms into the default geronimo web container. All filters, servlets and listeners will be able to be configured from the standard servlet 2.4 web.xml deployment descriptor. EJBs deployed within an EAR that use link resolution should also be able to be resolved. -Any geronimo specific configuration will be done via the JSR88 deployment plan associated with -the deployment. The deployment plan will include any mappings required to JNDI resources -or specific web container configurations. +Any geronimo specific configuration will be done via a JSR88 deployment plan associated with +the deployed webapplication or EAR. The deployment plan will include any mappings required to JNDI resources or references to specific web container configurations. Optional WEB-INF/"impl"-web.xml files may be used for Jetty/Tomcat/etc specific configuration, but their use will be discouraged for all but exceptional cases. Instead, implementation specific configuration should either be done via an extensible deployment plan or avoided by integration into common geronimo services. @@ -41,8 +40,7 @@ host and/or domain names. Virtual hosts may be configured for logging, security, statistics, etc. A webapp may be targetted to a specific virtual host at deployment time. If a targeted virtual -host does not exist, this may result in either a validation error or the creation of a -dynamic virtual host with default configuration. +host has not been configured and started on the server, this will result in a error when the webapp is started. == Physical hosts == @@ -141,8 +139,12 @@ == Configuration == -Web applications will use a geronimo-web.xml file for their geronimo specific configuration. They -may also have impl-web.xml for implementation dependent configuration, but this is to be discouraged -in all but exceptional cases. +Web applications should be deployed with only the standard deployment descriptors in their +WEB-INF directories. Geronimo will use the associated JSR88 deployment plan to +provide geronimo and extensible implementation configuration. + +The use of impl-web.xml for implementation dependent configuration may be supported but this +is to be discouraged in all but exceptional cases. + The other web components will be configured via the GBean mechanism which may use *-service.xml files.
