Jump to: navigation, search

Jetty/Feature/Deployment Bindings

< Jetty‎ | Feature
Revision as of 14:01, 23 April 2013 by Jesse.mcconnell.gmail.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Jetty 7 and Jetty 8 are now EOL (End of Life)

All development and stable releases are being performed with Jetty 9.
This wiki is now officially out of date and all content has been moved to the Jetty Documentation Hub

Direct Link to updated documentation: http://www.eclipse.org/jetty/documentation/current/configuring-deployment.html

Jetty provides capability to tap into the application lifecycle of the deployment manager. This is achieved with deployment bindings.


There are a handful of bindings that exist within the core distribution of jetty.

  • StandardDeployer
    • deploying
    • Standard binding that deals with deploying a webapp
  • StandardStarter
    • starting
    • Standard binding that deals with starting a webapp
  • StandardStopper
    • stopping
    • Standard binding that deals with stopping a webapp
  • StandardUndeployer
    • undeploying
    • Standard undeployer that deals with undeploying a webapp
  • DebugBinding
    • <any specified>
    • attaches a binding and prints logging information of a context going through the specified binding target
  • GlobalWebappConfigBinding
    • deploying
    • allows the user to override various settings of a webapp's context globally for all contexts

       <Call name="addLifeCycleBinding">
           <New class="org.eclipse.jetty.deploy.bindings.GlobalWebappConfigBinding" >
             <Set name="jettyXml">file://<Property name="jetty.home" default="." />/etc/global-webapp-context-config.xml</Set>

  • OrderedGroupBinding
    • <any specified>
    • allows the user to specific a specific order for bindings to process in a given binding target