Jump to: navigation, search

Difference between revisions of "Jetty/Tutorial/Embedding Jetty"

Line 38: Line 38:
 
* Select one or many Handlers to call (see [ http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/server/handler/HandlerCollection.html HandlerCollection]
 
* Select one or many Handlers to call (see [ http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/server/handler/HandlerCollection.html HandlerCollection]
  
Complex request handling is typically built from multiple Handlers. Some of the handlers available in Jetty can be seen in the [http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/server/handler/package-frame.html org.eclipse.jetty.server.handler] package.
 
  
 
=== Hello World Handler ===
 
=== Hello World Handler ===
Line 69: Line 68:
  
 
The parameters passed to the handle method are:
 
The parameters passed to the handle method are:
;target:The target of the request which is either a URI or a name from a named dispatcher.
+
* target - The target of the request which is either a URI or a name from a named dispatcher.
;baseRequest:The Jetty mutable request object, which is always unwrapped.
+
* baseRequest -The Jetty mutable request object, which is always unwrapped.
;request:The immutable request object, which may have been wrapped.
+
* request - The immutable request object, which may have been wrapped.
;response:The response that may have been wrapped.
+
* response - The response that may have been wrapped.
  
 +
The handler sets the response status, content-type and marks the request as handled before it generates the body of the response using a writer.
  
  
 +
The following code from [http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/embedded/OneHandler.html OneHandler.java] shows how this handler can be used by a Jetty server:
 +
<pre>
 +
public static void main(String[] args) throws Exception
 +
{
 +
    Server server = new Server(8080);
 +
    server.setHandler(new HelloHandler());
 +
   
 +
    server.start();
 +
    server.join();
 +
}
 +
</pre>
  
 +
You now know everything you need to know to write a HTTP server based on Jetty.  However, typically complex request handling is typically built from multiple Handlers and we will look in later sections how handlers can be combined like aspects.
 +
Some of the handlers available in Jetty can be seen in the [http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/server/handler/package-frame.html org.eclipse.jetty.server.handler] package.
  
  

Revision as of 04:40, 27 July 2009



Introduction

Jetty has a slogan "Don't deploy your application in Jetty, deploy Jetty in your application". What this means is that Jetty as an alternative to bundling your application as a standard WAR to be deployed in Jetty, Jetty is designed to be a software component that can be instantiated and used in a java program just like any POJO.

This tutorial takes you step by step from the simplest jetty server instantiation, through programmatically, to running multiple web applications with standards based deployment descriptors.

The source for most of these examples is part of the standard jetty project.

Details

To embed a Jetty server, the following steps are typical:

  1. Create the server
  2. Add/Configure Connectors
  3. Add/Configure Handlers
  4. Add/Configure Servlets/Webapps to Handlers
  5. start the server
  6. wait (join the server to prevent main exiting).

Servers

The following code from SimplestServer.java will instantiate and run the simplest possible Jetty server:

public class SimplestServer
{
    public static void main(String[] args) throws Exception
    {
        Server server = new Server(8080);
        server.start();
        server.join();
    }
}

This runs a HTTP server on port 8080. It is not a very useful server as it has not handlers and thus will return a 404 error for every request.

Handlers

In order to produce a response to a request, Jetty requires a Handler to be set on the server. A handler may:


Hello World Handler

The following code from HelloHandler.java shows a simple hello world handler:

public class HelloHandler extends AbstractHandler
{
    final String _greeting;
    final String _body;
    
    public HelloHandler()
    {
        _greeting="Hello World";
        _body=null;
    }
    
    public void handle(String target, Request baseRequest, HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException
    {
        response.setContentType("text/html");
        response.setStatus(HttpServletResponse.SC_OK);
        baseRequest.setHandled(true);
        
        response.getWriter().println("<h1>"+_greeting+"</h1>");
        response.getWriter().println("from " + ((Request)request).getConnection().getConnector().getName());
        response.getWriter().println("<br/>");
        if (_body!=null)
            response.getWriter().println(_body);
    }
}

The parameters passed to the handle method are:

  • target - The target of the request which is either a URI or a name from a named dispatcher.
  • baseRequest -The Jetty mutable request object, which is always unwrapped.
  • request - The immutable request object, which may have been wrapped.
  • response - The response that may have been wrapped.

The handler sets the response status, content-type and marks the request as handled before it generates the body of the response using a writer.


The following code from OneHandler.java shows how this handler can be used by a Jetty server:

public static void main(String[] args) throws Exception
{
    Server server = new Server(8080);
    server.setHandler(new HelloHandler());
    
    server.start();
    server.join();
}

You now know everything you need to know to write a HTTP server based on Jetty. However, typically complex request handling is typically built from multiple Handlers and we will look in later sections how handlers can be combined like aspects. Some of the handlers available in Jetty can be seen in the org.eclipse.jetty.server.handler package.


Connectors

Handler Collections

File Server

Servlets

Context

ServletContext

WebApplicationContext