This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I was asked to analyze developing a product for a new company. In the past my experience has been with Apache and I was thinking about using JBoss for the production web server. Does the book get into the pros and cons of using JBoss for a production environment and why would someone choose JBoss over other web servers available (ex: Apache, WebLogic, etc)
Apache is an open source organisation. Are you asking about Apache Http Server? If so, JBoss is an application server, not a web server. You cannot compare an web server with an application server. Use an application server when you need the extra functionality it provides otherwise stick to a plain old Http server. Or are you asking about Apache Tomcat? If so, similar criteria apply, use the one most appropriate to the technologies you utilize.
JBoss AS is built on top of Apache Tomcat. It has added an EJB container to it and enhanced the EL a bit. If you need EJB, then you can scrap Tomcat from your list. It simply doesn´t support EJB´s. If you don´t need EJB´s, then you have to decide whether that EJB feature of JBoss is useful at any way. If not, then you can perfectly use Tomcat. Or if you like JBoss EL above standard EL, then you may consider JBoss AS.
After all, just find out the features/pros/cons/whatever and check if you need it sooner or later. As with every other choice you make in your life.
This isn't right. It is build on a JMX backed "micro kernel" into which various services are added. Tomcat is one of those services. There is a lot more to JBoss AS than just an EJB container and Tomcat!
Joined: Oct 08, 2006
OK, let´s rephrase it: JBoss took Apache Tomcat and built a JMX bus around it to make EJB integration able.
And JBoss AS 5.0.0 moved from a JMX Kernel base to a microcontainer base, thus most services are POJO-based. Of course, one of the primary services is a JMX servies which then hosts those services that have not yet been converted to the microcontainer.
In general, JBoss AS is a certified Java EE 5 application server. As such, it is required to provide a large number of services (see http://java.sun.com/javaee/technologies/ for a list) and uses various other projects to provide many of those services.
Check out chapter 1 of the book, it is a free download. That has some information on why to use JBoss AS. But we do not go into a detailed comparison with other app server.