What You’ll Create

A WAR application which will contain Javalin without Jetty. You can drop this WAR file into any Servlet 3.0 container.

Getting Started

The easiest way to get started is to clone the javalin-tomcat-embed-example example application:

git clone https://github.com/tipsy/javalin-tomcat-embed-example
cd javalin-tomcat-embed-example
./gradlew clean appRun

This will run Gradle Gretty plugin which in turn launches this WAR app in Tomcat. When the server boots, you can access the REST endpoint simply by typing this in your terminal, or opening http://localhost:8080/rest :

curl localhost:8080/rest/

Looking At The Sources

The project is using Gradle to do standard stuff: declare the project as WAR and uses the Gradle Gretty Plugin to easily launch the WAR app in Tomcat (using the appRun task).

The interesting bit is the dependencies stanza which includes Javalin but omits the Jetty dependency:

dependencies {
    compile("io.javalin:javalin:2.4.0") {
        exclude(mapOf("group" to "org.eclipse.jetty"))
        exclude(mapOf("group" to "org.eclipse.jetty.websocket"))

The servlet itself is very simple:

@WebServlet(urlPatterns = ["/rest/*"], name = "MyRestServlet", asyncSupported = false)
class MyRestServlet : HttpServlet() {
    val javalin = EmbeddedJavalin()
            .get("/rest") { ctx -> ctx.result("Hello!") }

    override fun service(req: HttpServletRequest, resp: HttpServletResponse) {
        javalin.service(req, resp)

Note: You must remember to use the EmbeddedJavalin class, which has been carefully designed to not to depend on Jetty. Using the original Javalin class will make the WAR app fail to start with java.lang.ClassNotFoundException: org.eclipse.jetty.server.Server.

The Servlet container will automatically auto-discover the servlet (since it’s annotated with @WebServlet); any requests to the servlet will be directed straight to Javalin which will then take care of handling the request properly.