Brian has 10+ years of experience as a technology leader and architect in a wide variety of settings from early startups to Fortune 500 companies. With experience delivering SaaS solutions in business intelligence, artificial intelligence and VoIP, his current focus is big data and analytics. Brian leads the Virgil project on Apache Extras, which is a services layer built on Cassandra that provides REST, Map/Reduce, Search and Distributed Processing capabilities. Brian is a DZone MVB and is not an employee of DZone and has posted 62 posts at DZone. You can read more from them at their website. View Full User Profile

Virgil goes DropWizard... who needs war files?

02.02.2012
| 5469 views |
  • submit to reddit

For years now I've been saying that J2EE may be dead (or dying).  Wherever possible, people are trying to cut down on code and configuration.  The lighter the better.  These days, even Tomcat seems heavy for the light-weight services we want to deploy.  Enter DropWizard.

Thanks goes to Coda Hale for putting together DropWizard, a rock-solid lightweight REST stack.  Its got everything you could want: configuration, metrics, parsing, health checks, etc.  It can even serve up static content.

With all those features, who needs war files?

Recently we contributed to DropWizard, adding the ability to serve up static content from the root url, which allowed us to port Virgil over.  Since Virgil has an entirely ExtJS based UI, static content is all we needed for the UI.

We just released a new version Virgil with DropWizard under the covers.

Using DropWizard, Virgil now provides an Admin UI.  Additionally, there are additional configuration parameters for logging and the http server.

If you get a chance, take a look at DropWizard.   It might just have you replacing your old servlet container. 

From http://brianoneill.blogspot.com/2012/01/virgil-goes-dropwizard-who-needs-war.html

Published at DZone with permission of Brian O' Neill, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)