Apache tomcat只是一个serverlet容器，它不支持企业Java应用程序(JEE)。JBoss和Glassfish支持JEE应用，但Glassfish比JBoss服务器重得多:参考幻灯片

Apache tomcat只是一个serverlet容器，它不支持企业Java应用程序(JEE)。JBoss和Glassfish支持JEE应用，但Glassfish比JBoss服务器重得多:参考幻灯片

Tomcat只是一个servlet容器，也就是说，它只实现servlet和JSP规范。Glassfish和JBoss是完整的Java EE服务器(包括EJB、JMS等)，Glassfish是最新Java EE 6堆栈的参考实现，但JBoss在2010年还没有完全支持它。

jboss和glassfish包括一个servlet容器(如tomcat)，但是两个应用服务器(jboss和glassfish)也提供了一个bean容器(以及一些我想象的其他东西)。

Tomcat is merely an HTTP server and Java servlet container. JBoss and GlassFish are full-blown Java EE application servers, including an EJB container and all the other features of that stack. On the other hand, Tomcat has a lighter memory footprint (~60-70 MB), while those Java EE servers weigh in at hundreds of megs. Tomcat is very popular for simple web applications, or applications using frameworks such as Spring that do not require a full Java EE server. Administration of a Tomcat server is arguably easier, as there are fewer moving parts.

However, for applications that do require a full Java EE stack (or at least more pieces that could easily be bolted-on to Tomcat)... JBoss and GlassFish are two of the most popular open source offerings (the third one is Apache Geronimo, upon which the free version of IBM WebSphere is built). JBoss has a larger and deeper user community, and a more mature codebase. However, JBoss lags significantly behind GlassFish in implementing the current Java EE specs. Also, for those who prefer a GUI-based admin system... GlassFish's admin console is extremely slick, whereas most administration in JBoss is done with a command-line and text editor. GlassFish comes straight from Sun/Oracle, with all the advantages that can offer. JBoss is NOT under the control of Sun/Oracle, with all the advantages THAT can offer.

JBoss和Tomcat都是Java servlet应用服务器，但JBoss的功能远不止这些。两者之间的实质区别是JBoss提供了完整的Java企业版(Java EE)堆栈，包括企业JavaBeans和许多其他技术，这些技术对于开发企业Java应用程序的开发人员非常有用。

Tomcat的限制要大得多。可以这样想，JBoss是一个包含servlet容器和web服务器的Java EE堆栈，而Tomcat在很大程度上是一个servlet容器和web服务器。