The great Java app server debate with Tomcat/TomEE & JBoss


News: The great Java app server debate with Tomcat/TomEE & JBoss

  1. **Tomcat and TomEE** Prepared by Simon Maple: It’s easy to see why Tomcat has grown in popularity to be the most popular application server around the world today. Tomcat has been around for a fair time now, with it’s very stable runtime and large, responsive community, including other vendors basing their products on the Tomcat core. It’s fast has has good tooling built into many IDEs but for me it lacks in it’s config. Yes, if you’re used to Tomcat and have used it for a while it may not be a problem, but having worked for IBM and seeing how the WebSphere config structure/mess has shrunk into a single file, I believe Tomcat has a fair bit of room for improvement. If IBM can do it… ;o) The support is community based, but as mentioned if you need more, there are guaranteed vendor contracts that are available. The final big plus for Tomcat is the price. It’s free and opensource – that’s awesome! Everything open source is great, right?….. **JBoss AS 7 (aka WildFly)** Prepared by Oleg Shelajev: JBoss AS7 is an outstanding piece of software. It has both big company support and a superb community behind it. The balance of a fully open-source solution versus subscription-based EAP covers almost all possibilities. At the same time, this EAP nuance might be a bit confusing; IMHO, holding the bug-fixes in the EAP version and not providing them into the community edition version is questionable. At the same time, if you only care about the performance and support for standards, JBoss is a safe choice. Hopefully, WildFly will continue to be awesome and, as they say, “#@*%ing fast”. *** Look for the upcoming Rebel Labs report, which not only reviews, but also compares Tomcat, JBoss, Jetty, Glassfish, Weblogic and IBM's Websphere and Liberty Profile. For instant gratification:
  2. Not sure why it looks like this, but please check out the ZeroTurnaround blog for all content:
  3. Perhaps I'm being too negative and times have probably changed my POV.  Honestly, it makes sense that Tomcat goes into EE world but what made Tomcat popular is because it wasn't EE.  I do realize Java EE6/7 is much better then before.  However, I keep using Tomcat + Spring approach due to testability.  With this tech stack, I can write TRUE JUnit integration test that uses real transactions and other EE services. I have seen weblogic/websphere/etc... where they put MOCK on the integration test using other open source libraries.  This is the part I don't understand.. if I'm writing a integration test then I want truly want to test the code that will be deployed.  Again, my POV on this maybe very outdated and now they have a way to write good integration JUnits.  Please correct me if I'm wrong.

  4. Look into Arquillian:
  5. Yes, you're wrong. I mean, J2EE is a set of standard APIs. Regardless of the server you choose, testability isn't affected. YOU write the tests. YOU run the tests. The server doesn't prevent or hinder you in any way. Why would you expect your tests to run differently on Tomcat/Spring vs. WebLogic/EJB?