Message-ID: <1308515121.41478.1371653132317.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_41477_326921621.1371653132317" ------=_Part_41477_326921621.1371653132317 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The WebApp Dep= loyer is for static deployment standard WAR files and webapps with lit= tle or no Jetty specific customization. For hot deployment of customized co= ntexts, use the Context Deployer= .
The WebAppDeployer replaces the static method call org.mortbay.jetty.web= app.WebAppContext.addWebApplications that was used to discover and deploy w= ebapplication during startup. This method is now deprecated, but still wor= ks (by calling an instance of WebApplicationDeployer).
The basic operation of WebAppDeployer is to scan a directory at startup = for WAR files or webapp directories and the deploy the webapplications foun= d. Typically this is done from a jetty.xml file:
The WebAppDeployer is added to the server as a LifeCycle. This simply m= eans that the deployer will be started and stopped with the server. Ie whe= n server.start() is called, then start will also be called on the deployer.=
The context passed in is a reference to a HandlerContai= ner in which the discovered webapps will be deployed. This is normally an i= nstance of ContextHandlerCollection.
The webAppDir is a file path or URL to the directory to= scan for webapplications. Zip files ending with .war or .zip are deployed.= Directories not call CVS are also deployed. The basename of the war (eg f= oo from foo.war) or the directory name are used as the context path of the = discovered webapps, unless the name is "root", in which case the = context path of / is used.
The parentLoaderPriority parameter is a boolean that se= lects of the standard java parent first delegation Classloading will be used or the servlet specification = webapp Classloading priority.= p>
If the extract parameter is true, any packed war or zip= files will first be extracted to a temporary directory before being deployed. This is advisable = if there are uncompiled JSPs in the web apps.
If the allowDuplicates parameter is false, the discover= ed webapps will be checked against existing deployed webapps and will not b= e deployed if the same context path or war files is already deployed (perha= ps by another deployer).
The defaultsDescriptor parameter allows an alternative = webdefault.xml to be set on t= he discovered web applications. The webdefault.xml file is used to control the configuration of the JSP = and Default servlets.------=_Part_41477_326921621.1371653132317--