Francesco Marchioni, thanks for participating in the book giveaway.
The question I have about JBoss, now Wildfly, is what does it give me that I do not get from Tomcat? Please understand, I'm not challenging the value of Wildfly or trying to assert that Tomcat is all I could ever need for running JVM web applications. I just want to understand what Wildfly does better. I assume this is a common question, I hope it's not too annoying to see it again.
From the book description, I see you've been involved with JBoss since 2000 and writing books related to it since 2009. I'm sure you know your domain. I'm curious how well you know the rest of the Java and non-Java webserver world compared to Wildfly.
Tomcat is a basic J2EE server that does not provide the full J2EE or JEE stacks. Stuff like EJBs and JMS, for example. Tomcat does servlets and JSPs and provides basic services such as database connection pools, but nowhere near all that Enterprise Java has to offer.
JBoss/Wildfly, on the other hand, is the full stack and then some. In fact, it has a copy of Tomcat embedded inside it for the servlet/JSP support, but that's just one of its components.
So why one or why the other?
Tomcat is good if all you need is basic services. It's small, easy to set up, doesn't require much resources and it's quick to startup and shut down. JBoss/Wildfly isn't as lightweight, but it can handle apps that need industrial-grade services. To get Tomcat to run JavaServer Faces webapps, you have to actually embed a copy of the JSF implementation into each webapp's WAR. In full-stack JEE, JSF is part of the server itself. Likewise with EJB support, mail and messaging, and all the other amenities.
And, of course, you can get commercial support for Wildfly direct from its creators. Tomcat doesn't have that.
When it comes to destroying a civilization, gas chambers cannot hold a candle to echo chambers.
Proudly marching to the beat of a different kettle of fish... while reading this tiny ad
how do I do my own kindle-like thing - without amazon