Contact the core Jetty developers at www.webtide.com
private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery

Using the WebApp Provider

The WebApp Provider is for static deployment of standard WAR files and webapps with little or no Jetty-specific customization. For hot deployment of customized contexts, use the ContextProvider.

The basic operation of the WebAppProvider is to scan a directory at startup for WAR files or webapp directories and to deploy the web applications found. Typically this is done from a jetty.xml style file; in the jetty distribution the name of this file is jetty-webapps.xml:

 
 <Configure id="Server" class="org.eclipse.jetty.server.Server">
    <Ref id="DeploymentManager">
          <Call id="webappprovider" name="addAppProvider">
            <Arg>
              <New class="org.eclipse.jetty.deploy.providers.WebAppProvider">
                <Set name="monitoredDirName"><Property name="jetty.home" default="." />/webapps</Set>
                <Set name="defaultsDescriptor"><Property name="jetty.home" default="."/>/etc/webdefault.xml</Set>
                <Set name="scanInterval">1</Set>
                <Set name="contextXmlDir"><Property name="jetty.home" default="." />/contexts</Set>
                <Set name="extractWars">true</Set>
              </New>
            </Arg>
          </Call>
    </Ref>
</Configure>

    

This works as follows:

See an error or something missing?
Contribute to this documentation at Github!