Make JAR, not WAR

[ahornace]

Recently I watched some videos by Josh Long for Spring Boot where he said the quote "Make JAR, not WAR". He provided some good arguments about why embedded containers are the way to go.

Basically the benefits are that you can have one service-like application and you do not have to worry about the servlet container at all. It makes the deployment of the application far more easier and there would be less issues regarding the Tomcat version just because it would be provided by us.

Disadvantages: if you have multiple applications running, then each of them has its own servlet container.

With Spring Boot it works mostly out of the box. However, I quickly tried this yesterday on OpenGrok and I had some problems with the embedded Tomcat -> I was not able to load the webapps directory from the binary file. Although embedded Jetty seems to support this. I tried following this guide: https://devcenter.heroku.com/articles/create-a-java-web-application-using-embedded-tomcat

This is just a suggestion. So, what do you guys think? :)

[tarzanek]

I saw jenkins doing the same thing with jetty(?), perhaps there we can have a look for working experience?

[tarzanek]

ah, ok, it's wrapper(?) on top of jetty - http://winstone.sourceforge.net/

[ahornace]

ah, ok, it's not jetty but http://winstone.sourceforge.net/

The web mentions only Servlet 2.5 support. However, the one developed by Jenkins team should be compatible with 3.1: https://github.com/jenkinsci/winstone