Contact the core Jetty developers at
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
Skip to end of metadata
Go to start of metadata
If you are experiencing ClassNotFound exceptions using JAAS with Jetty6.0.x the workaround is to put some extra configuration into the jetty.xml file to make the jetty jaas classes visible.
For Jetty Standalone
CONTEXT PATH is the context path you want to assign to your webapp
LOCATION OF WEBAPP is the location of the war or expanded war of your webapp
For the Jetty Maven Plugin
Use a jetty-web.xml or a jetty-env.xml file to set the server classes, like so: