Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Then, ensure that your custom webdefault.xml file is applied to all of your webapps by editing all of your relevant jetty configuration files (eg . You can do that by changing the configuration of the WebAppDeployer in etc/jetty.xml, etc/jetty-plus.xml and any custom files you may have) and indicating the location of the custom file:

Code Block
xml
xml
    <Call name="addLifeCycle">
      <Arg>
        <New class="org.mortbay.jetty.webappdeployer.WebAppContext" name="addWebApplications"WebAppDeployer">
      <Arg><Ref     <Set name="contexts"><Ref id="ServerContexts"/></Arg>Set>
      <Arg>./webapps</Arg>    <Set name="webAppDir"><SystemProperty name="jetty.home" default="."/>/webapps</Set>
      <Arg>org/mortbay/jetty/webapp/webdefault.xml</Arg>    <Set name="parentLoaderPriority">false</Set>
          <Set name="extract">true</Set>
          <Set name="allowDuplicates">false</Set>
          <Set name="defaultsDescriptor">/home/fred/jetty/mywebdefaults.xml</Set> <!-- changeset to your newcustomized defaults file path -->
      <Arg type="boolean">True</Arg>  </New>
      <Arg type="boolean">False<</Arg>
    </Call>

Alternatively, if you have individually configured your webapps with context xml files, you need to call the WebAppContext.setDefaultsDescriptor(String path) method:

...

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