Jetty webapp osgi way

I will show how to expose simple Jetty OSGi service and use it to register hello world webapp. This app will serve static content from OSGi bundle and implement sample request handler under ServiceMix 4.Code is available here: http://github.com/rafalrusin/jetty-service
Alternative solutions are: using standard OSGi HTTP service http://www.osgi.org/javadoc/r4v42/org/osgi/service/http/HttpService.htmlto register servlet; and wrap existing WAR application using PAX WEB http://wiki.ops4j.org/display/paxweb/Pax+Web.I won’t consider those two, since Jetty itself provides flexible way to handle webapps (including registering servlets). So those two are unnecessary overhead and are less flexible. Anyway those two are usually implemented on top of Jetty.
So the first thing to do is to create Jetty OSGi service. Basicly it will be a Spring Bean exposed to OSGi. Following snippet does the job:

<bean id="jetty-service" class="org.apache.jetty.service.JettyServiceImpl" init-method="init" destroy-method="destroy"/>
<osgi:service id="jetty-service-osgi" ref="jetty-service" interface="org.apache.jetty.service.api.JettyService" />

This will expose jetty-service to OSGi. All other components, which connect to it will wait automaticly until it’s registered.Exposed interface has following methods:

public Handler registerApp(String name, Handler handler) throws Exception;
public void unregisterApp(Handler handler) throws Exception;

Those will be invoked to register Hello World application. JettyServiceImpl on the other hand, starts embedded Jetty Server and handles apps registration.
package org.apache.jetty.service;

import org.apache.jetty.service.api.JettyService;
import org.mortbay.jetty.Handler;
import org.mortbay.jetty.Server;
import org.mortbay.jetty.handler.ContextHandler;
import org.mortbay.jetty.handler.ContextHandlerCollection;

public class JettyServiceImpl implements JettyService {
    private Server server;
    private ContextHandlerCollection rootContext;

    public void init() throws Exception {
        server = new Server(8080);
        rootContext = new ContextHandlerCollection();
        server.setHandler(rootContext);
        server.start();
    }

    public void destroy() throws Exception {
        server.stop();
    }

    public Handler registerApp(String name, Handler handler) throws Exception {
        server.stop();
        ContextHandler h = rootContext.addContext("/" + name, name);
        h.setHandler(handler);
        server.start();
        return h;
    }

    public void unregisterApp(Handler handler) throws Exception {
        server.stop();
        rootContext.removeHandler(handler);
        server.start();
    }
}

Next step is to implement sample web app. First, we need to connect jetty-service bean to make it visible in our app.

  <osgi:reference id="jetty-service" interface="org.apache.jetty.service.api.JettyService" bean-name="jetty-service"/>

<bean class=“org.apache.jetty.service.example.HelloWorld” init-method=“init” destroy-method=“destroy”>
<property name=“jettyService” ref=“jetty-service”/>
Then, we need to implement sample app.

package org.apache.jetty.service.example;

import java.io.IOException;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import org.apache.jetty.service.api.JettyService;
import org.apache.jetty.service.util.BundleResource;
import org.mortbay.jetty.Handler;
import org.mortbay.jetty.HttpConnection;
import org.mortbay.jetty.Request;
import org.mortbay.jetty.handler.AbstractHandler;
import org.mortbay.jetty.handler.ContextHandler;
import org.mortbay.jetty.handler.ContextHandlerCollection;
import org.mortbay.jetty.handler.ResourceHandler;

public class HelloWorld {
    private JettyService jettyService;
    private Handler registered;

    public void setJettyService(JettyService jettyService) {
        this.jettyService = jettyService;
    }

    public void init() throws Exception {
        ContextHandlerCollection handler = new ContextHandlerCollection();

        handler.addContext("/app", "app").setHandler(new AbstractHandler() {
            public void handle(String target, HttpServletRequest request,
                               HttpServletResponse response, int arg3) throws IOException,
                    ServletException {
                response.setContentType("text/html");
                response.setStatus(HttpServletResponse.SC_OK);
                response.getWriter().println(
                    "Hello World from Java"
                    + request.getParameterMap()
                );

                Request base_request = (request instanceof Request) ? (Request) request : HttpConnection.getCurrentConnection().getRequest();
                base_request.setHandled(true);
            }
        });

        ResourceHandler resourceHandler = new ResourceHandler();
        resourceHandler.setBaseResource(new BundleResource(getClass().getResource("/static")));
        ContextHandler contextHandler = handler.addContext("", "");
        contextHandler.setHandler(resourceHandler);

        registered = jettyService.registerApp("helloWorld", handler);
    }

    public void destroy() throws Exception {
        jettyService.unregisterApp(registered);
    }
}

Here, we register sample request handler at ‘app’ sub path and serve static content from jar using BundleResource. Last thing is registering app using jettyService under ‘helloWorld’ context. So our application will be exposed under http://localhost:8080/helloWorld/ address.
ServiceMix has also so called features. This is the way to collect multiple dependencies under a single name. So we have to create features.xml file, like this:

<features>
    <feature name="jetty-service" version="${project.version}">
        <bundle>mvn:org.apache.jetty.service/service/${project.version}bundle> feature>

<feature name=“example-jetty-service-helloworld” version=“${project.version}”>
<feature version=“${project.version}”>jettyservicefeature>
<bundle>mvn:org.apache.jetty.service/examplehelloworld/${project.version}bundle>
feature>
features>

Basicly, we can provide particular dependencies for our project.
Next, we do ‘mvn install’ on our project and run apache-servicemix-4.2.0-fuse-01-00/bin/servicemix karaf console. On the console, we need to type following commands:

features:addUrl mvn:org.apache.jetty.service/service-karaf/0.1.0-SNAPSHOT/xml/features
features:install example-jetty-service-helloworld
osgi:list
[ 230] [Active ] [ ] [Started] [ 60] Unnamed – org.apache.jetty.service:service:bundle:0.1.0-SNAPSHOT (0.1.0.SNAPSHOT)
[ 231] [Active ] [ ] [Started] [ 60] Unnamed – org.apache.jetty.service:example-helloworld:bundle:0.1.0-SNAPSHOT (0.1.0.SNAPSHOT)
Now, we can enter http://localhost:8080/helloWorld/ to test our app.
And that’s it. OSGi and ServiceMix 4 features enable easy way to use dynamic modules in web apps. For example, it’s veryeasy to build simple web framework with loadable components on page (something like mini implementation of Portlets).

You May Also Like

Private fields and methods are not private in groovy

I used to code in Java before I met groovy. Like most of you, groovy attracted me with many enhancements. This was to my surprise to discover that method visibility in groovy is handled different than Java!

Consider this example:

class Person {
private String name
public String surname

private Person() {}

private String signature() { "${name?.substring(0, 1)}. $surname" }

public String toString() { "I am $name $surname" }
}

How is this class interpreted with Java?

  1. Person has private constructor that cannot be accessed
  2. Field "name" is private and cannot be accessed
  3. Method signature() is private and cannot be accessed

Let's see how groovy interpretes Person:

public static void main(String[] args) {
def person = new Person() // constructor is private - compilation error in Java
println(person.toString())

person.@name = 'Mike' // access name field directly - compilation error in Java
println(person.toString())

person.name = 'John' // there is a setter generated by groovy
println(person.toString())

person.@surname = 'Foo' // access surname field directly
println(person.toString())

person.surname = 'Bar' // access auto-generated setter
println(person.toString())

println(person.signature()) // call private method - compilation error in Java
}

I was really astonished by its output:

I am null null
I am Mike null
I am John null
I am John Foo
I am John Bar
J. Bar

As you can see, groovy does not follow visibility directives at all! It treats them as non-existing. Code compiles and executes fine. It's contrary to Java. In Java this code has several errors, pointed out in comments.

I've searched a bit on this topic and it seems that this behaviour is known since version 1.1 and there is a bug report on that: http://jira.codehaus.org/browse/GROOVY-1875. It is not resolved even with groovy 2 release. As Tim Yates mentioned in this Stackoverflow question: "It's not clear if it is a bug or by design". Groovy treats visibility keywords as a hint for a programmer.

I need to keep that lesson in mind next time I want to make some field or method private!