# wiztowar
**Repository Path**: mirrors_twilio/wiztowar
## Basic Information
- **Project Name**: wiztowar
- **Description**: Build WARs from your Dropwizard apps
- **Primary Language**: Unknown
- **License**: MIT
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No
## Statistics
- **Stars**: 0
- **Forks**: 0
- **Created**: 2021-10-22
- **Last Updated**: 2025-09-21
## Categories & Tags
**Categories**: Uncategorized
**Tags**: None
## README
WizToWar - Have your cake and eat it too
========================================
WizToWar is a simple library that enables a [Dropwizard](http://dropwizard.io) service to also be deployable in a WAR container such as Tomcat.
By following the steps in the usage section below you will be able to create
both a Dropwizard jar and a WAR of the same service.
Caveat emptor:
--------------
* Only tested on Tomcat 7
* No support for bundles
* Many features untested
* Goes against the whole philosophy of Dropwizard...
Usage
------
Include the wiztowar jar as a dependency:
```xml
com.twilio
wiztowar
1.3
```
Create a new class for your application like this:
```java
package com.twilio.mixerstate;
import com.google.common.io.Resources;
import com.twilio.wiztowar.DWAdapter;
import com.yammer.dropwizard.Service;
import java.io.File;
import java.net.URISyntaxException;
import java.net.URL;
public class MixerStateDWApplication extends DWAdapter {
final static MixerStateService service = new MixerStateService();
/**
* Return the Dropwizard service you want to run.
*/
public Service getSingletonService(){
return service;
}
/**
* Return the File where the configuration lives.
*/
@Override
public File getConfigurationFile() {
URL url = Resources.getResource("mixer-state-server.yml");
try {
return new File(url.toURI());
} catch (URISyntaxException e) {
throw new IllegalStateException(e);
}
}
}
```
Create a main/webapp/WEB-INF/web.xml file:
------------------------------------------
```xml
com.twilio.mixerstate.MixerStateDWApplication
```
Make sure you also build a WAR artifact
---------------------------------------------
There are two alternatives to building a war:
### a. Add instructions to also build a WAR
This goes in `` section:
```xml
org.apache.maven.plugins
maven-war-plugin
2.4
default-war
package
war
target/webapp
```
### b. Change packaging of your Dropwizard service
If you do not intend to run the Dropwizard service standalone, you can simply
change the "packaging" element in pom.xml to be "war" instead of "jar".