Skip to main content

Run/Debug java webapp without packaging/deploying it with Jetty and under Maven2

Goals

As the title mentioned, run(with maven2 command or in IDE)/debug(in IDE) java webapp without packaging the war file, installing/configuring any appserver like tomcat or deploying your code to anywhere. The practice will be "compile and run".

Why Jetty?

Jetty is a lightweight, flexible and embeddable Java servlet container. It's so flexible that it can even start servicing a webapp directly from given classpath and a web.xml file without assembling them into a standard webapp.

Step by step

Introduce several dependencies into you pom file. This is required whatsoever if you want to run/debug jetty in IDE and make sure the servlet-api, xercesImpl and java tools.jar(if you want to run JSP) are in dependency list.

<dependency>
  <groupId>jetty</groupId>
  <artifactId>org.mortbay.jetty</artifactId>
  <version>5.1.10</version>
  <scope>runtime</scope>
</dependency>
<dependency>
  <groupId>jetty</groupId>
  <artifactId>jasper-runtime</artifactId>
  <version>4.2.20RC0</version>
  <scope>runtime</scope>
</dependency>
<dependency>
  <groupId>jetty</groupId>
  <artifactId>jasper-compiler</artifactId>
  <version>4.2.20RC0</version>
  <scope>runtime</scope>
</dependency>
Create jetty config file PROJECT_BASE_DIR/src/test/config/jetty.xml, assuming the web.xml file is already under src/main/webapp/WEB-INF directory. Feel free to change the directory and port if you want.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"
      "http://jetty.mortbay.org/configure.dtd">
<Configure class="org.mortbay.jetty.Server">
  <Call name="addListener">
      <Arg>
          <New class="org.mortbay.http.SocketListener">
              <Set name="port">
                  <SystemProperty name="jetty.port" default="8081" />
              </Set>
          </New>
      </Arg>
  </Call>
  <Call name="addWebApplication">
      <Arg>/</Arg>
      <Arg>./src/main/webapp</Arg>
  </Call>
</Configure>
Now, after injecting add dependencies into you IDE(For eclipse, run mvn eclipse:eclipse [-DdownloadSources=true] or use m2eclipse eclipse plugin), you should be able to run/debug the webapp after the code compiles. A java application with org.mortbay.jetty.Server as main class and src/test/config/jetty.xml as argument will start the webapp on port 8081.

Jetty6.x required less jar file dependencies, particularly only one jetty jar file if you don't want to run JSP, and syntax of jetty.xml file will be different. Please look at http://www.mortbay.org for more details.

Comments

Post a Comment

Popular posts from this blog

Spring, Angular and other reasons I like and hate Bazel at the same time

For several weeks I've been trying to put together an Angular application served Java Spring MVC web server in Bazel. I've seen the Java, Angular combination works well in Google, and given the popularity of Java, I want get it to work with open source. How hard can it be to run arguably the best JS framework on a server in probably the most popular server-side language with  the mono-repo of planet-scale ? The rest of this post walks through the headaches and nightmares I had to get things to work but if you are just here to look for a working example, github/jiaqi/angular-on-java is all you need. https://github.com/jiaqi/angular-on-java Java web application with Appengine rule Surprisingly there isn't an official way of building Java web application in Bazel, the closest thing is the Appengine rule  and Spring MVC seems to work well with it. 3 Java classes, a JSP and an appengine.xml was all I need. At this point, the server starts well but I got "No ...
Post a Comment
Read more

Customize IdGenerator in JPA, gap between Hibernate and JPA annotations

JPA annotation is like a subset of Hibernate annotation, this means people will find something available in Hibernate missing in JPA. One of the important missing features in JPA is customized ID generator. JPA doesn't provide an approach for developer to plug in their own IdGenerator. For example, if you want the primary key of a table to be BigInteger coming from sequence, JPA will be out of solution. Assume you don't mind the mixture of Hibernate and JPA Annotation and your JPA provider is Hibernate, which is mostly the case, a solution before JPA starts introducing new Annotation is, to replace JPA @SequenceGenerator with Hibernate @GenericGenerator. Now, let the code talk. /** * Ordinary JPA sequence. * If the Long is changed into BigInteger, * there will be runtime error complaining about the type of primary key */ @Id @Column(name = "id", precision = 12) @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "XyzIdGenerator") @SequenceGe...
4 comments
Read more

A dozen things to know about AWS Simple Workflow in Eclipse and Maven

Amazon AWS Simple Workflow AWS Simple Workflow(SWF) from Amazon is a unique workflow solution comparing to traditional workflow products such as JBPM and OSWorkflow. SWF is extremely scalable and engineer friendly(in that flow is defined with Java code) while it comes with limitations and lots of gotchas. Always use Flow Framework The very first thing to know is, it's almost impossible to build a SWF application correctly without Flow Framework . Even though the low level SWF RESTful service API is public and available in SDK, for most workflow with parallelism, timer or notification, consider all possibilities of how each event can interlace with another, it's beyond manageable to write correct code with low-level API to cover all use cases. For this matter SWF is quite unique comparing to other thin-client AWS technologies. The SWF flow framework heavily depends on AspectJ for various purposes. If you are not familiar with AspectJ in Eclipse and Maven, this article ...
Post a Comment
Read more