Webapp runner is designed to allow you to launch an exploded or compressed war that is on your filesystem into a tomcat container with a simple
java -jar command. It supports the following version of Tomcat:
Clone and Build
git clone firstname.lastname@example.org:jsimone/webapp-runner.git mvn package
java -jar target/webapp-runner.jar path/to/my/project
java -jar target/webapp-runner.jar myProject.war
java -jar target/webapp-runner.jar --help
Prints out all arguments accepted
Using with Maven in your project
You can use the Maven dependency plugin to download webapp-runner as part of your build. This will eliminate the need for any external dependencies other than those specified in your build to run your application.
Add the following to your pom.xml:
<build> ... <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.3</version> <executions> <execution> <phase>package</phase> <goals><goal>copy</goal></goals> <configuration> <artifactItems> <artifactItem> <groupId>com.github.jsimone</groupId> <artifactId>webapp-runner</artifactId> <version>220.127.116.11</version> <destFileName>webapp-runner.jar</destFileName> </artifactItem> </artifactItems> </configuration> </execution> </executions> </plugin> </plugins> ... </build>
Now when you run
maven package webapp runner will be downloaded for you. You can then launch your application with:
$ java -jar target/dependency/webapp-runner.jar target/<appname>.war
Store your sessions in memcache
In versions 18.104.22.168 and newer support for a session manager that stores sessions in memcache is built in.
To use it add
--session-store memcache to your startup command:
$ java -jar target/dependency/webapp-runner.jar --session-store memcache target/<appname>.war
Then make sure that three environment variables are available for configuration: MEMCACHE_SERVERS, MEMCACHE_USERNAME, MEMCACHE_PASSWORD
Store your sessions in redis
In versions 22.214.171.124 and newer support for a session manager that stores sessions in redis is built in.
To use it add
--session-store redis to your startup command:
$ java -jar target/dependency/webapp-runner.jar --session-store redis target/<appname>.war
Then make sure that Redis environment variable is available for configuration: REDIS_URL
Using Tomcat behind a reverse proxy server
If you are using webapp-runner behind a proxy server, you can set the proxy base url within tomcat:
$ java -jar target/dependency/webapp-runner.jar --proxy-base-url http://example.com target/<appname>.war
If you pass an HTTPS base url, e.g. https://example.com, secure flag will be automatically added to session cookies. This indicates to the browser that cookies should only be sent over a secure protocol.
Running your application in Eclipse
Since your application will just be a standard webapp you can still use WTP and the traditional Tomcat integration points to run your application within Eclipse. However the containerless nature of webapp runner allows you to run from within Eclipse in a simpler way.
Start by importing your project into Eclipse. It is best to import it as an existing Maven project using the m2eclipse plugin.
Make your application dependant on webapp runner
Add the following dependency to your pom.xml:
<dependency> <groupId>com.github.jsimone</groupId> <artifactId>webapp-runner</artifactId> <version>126.96.36.199</version> <scope>provided</scope> </dependency>
This will cause Eclipse to include webapp-runner on the classpath of your project so that it can be used for launching. It won't affect the final artifact built for your application.
Create a launch configuration
- Right-click on your project and choose 'Debug As -> Debug Configurations...'
- From the 'Debug Configuration' window create a new 'Java Application' launch configuration by double-clicking on 'Java Application' in the left hand list or right-clicking on it and selecting 'New'
- Give your launch configuration a sensible name. Then enter the name of your project in the 'Project' box
- Enter 'webapp.runner.launch.Main' in the 'Main Class' box
- Click on the 'Arguments' tab and enter './src/main/webapp' in the 'Program Arguments' box
- Click 'Apply' and then 'Run'
Your application should start and you should see the log output in the Eclipse console. Since you have a debugger attached to your application you'll now see changes to your code get automatically loaded without restarting and can set breakpoints.
You can stop the application from the red square in the console pane or from the debug perspective. It can be restarted by right-clicking on the project and choosing your new launch configuration from the 'Debug As' menu or from the debug menu in the Eclipse toolbar (the icon with the little bug).
Note: webapp runner is now available in Maven Central. The version scheme has also chanaged to match the version of
Tomcat that it relies on. The format is
<tomcat version>.<minor webapp runner version>.
Versions 0.0.1 to 0.0.7 are still available at http://jsimone.github.com/webapp-runner/repository.
To run the entire suite of integration tests, use the following command:
$ mvn clean install -Pintegration-test
To run an individual integration test, use a command like this:
$ mvn clean install -Pintegration-test
Copyright (c) 2012, John Simone All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of John Simone nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.