JBoss5 Web Deployments
The war deployment layer has undergone a major revision to rewrite the deployers to use the VDF. The legacy jmx based org.jboss.web.AbstractWebContainer replaced by org.jboss.web.deployers.AbstractWarDeployer. The org.jboss.web.tomcat.tc6.Tomcat6 mbean service is replaced by org.jboss.web.tomcat.tc6.deployers.TomcatDeployer.
The legacy org.jboss.web.AbstractWebDeployer is replaced by org.jboss.web.deployers.AbstractWarDeployment. The org.jboss.web.tomcat.tc6.TomcatDeployer is replaced by org.jboss.web.tomcat.tc6.deployers.TomcatDeployment.
In addition, there are metadata deployers that remove the need for these deployers to parse any web.xml/jboss-web.xml:
An org.jboss.deployment.WebAppParsingDeployer translates a web.xml descriptor into a org.jboss.metadata.WebMetaData instance.
An org.jboss.deployment.JBossWebAppParsingDeployer translates a jboss-web.xml descriptor into the existing org.jboss.metadata.WebMetaData instance.
The deployers are packed up in the server/xxx/deployers/jbossweb-tomcat6.deployer directory.
An overview of the deployment process.
The relative order of the deployer defines the point at which it runs in the deployment process. The lower the order, the earlier the deployer runs. The relative ordering of the war-deployers-beans.xml deployers is:
The WebAppParsingDeployer runs first to parse the WEB-INF/web.xml into a org.jboss.metadata.WebMetaData object graph. It extends the org.jboss.deployers.plugins.deployers.helpers.ObjectModelFactoryDeployer will create kernel bean metadata to deploy these components directly to the microcontainer.
The source code for the tomcat deployers is located in the tomcat module of the jbossas project.