Using Jetty as an embedded server is far more different this time compared to version 5. The code have been overlhauled at least and uses the org.mortbay.jetty.Server against org.mortbay.http.HttpServer. If you have plans porting Jetty in your application, you may need these two important jars:
These are the ones needed for servlet. However, running Jetty with jsp is a different thing depending on the jdk version installed in your environment.
There are two versions of the jsp engine being used - JSP 2.0 and JSP 2.1. Their difference is basically simple. JSP 2.0 is being mandated by the JDK 1.4 or lower version while JSP 2.1 is called when used with JDK 1.5 version. Furthermore, the different jars used by those jsp versions are put on the classpath as well. Please be reminded that when using a standalone jetty, it will automatically choose which version of JSP it will used upon recognizing the JAVA runtime environment.
You may find these resources in the jetty_home\lib\jsp folder. You can call the Server class to serve for web applications. You can configure your own jetty.xml or call it in your Server class similar to this:
If you don't want to do webapps, then you can still use the Server class, and the various Connector implementations, but just use different Handler implementations. Have a look at what is going on near the bottom of the etc/jetty.xml file where it says: "Configure a context directly - no XML parser required". This is setting up a ContextHandler that can serve servlets and static content. The servlet setup isn't done by a web.xml file, but rather in API calls instead as you can see. The DefaultServlet impl is being used to serve static content. If you just want to serve static content, then you might have to create your own Handler using the DefaultServlet implementation as a guide.