why jboss-tomcat?

[gshilpa]

guys..
i have a big doubt & will be grateful to anybody who can help me with this one.

i am working with jboss-tomcat4.1 bundle.
for any web-application i need to make a war & deploy it in jboss's deploy folder.
so ultimately i use jboss's server to run any application.
Then what is the advantage of having tomcat bundled with jobss.

[jonlee]

JBoss is a lot of things, including an EJB container but it is not a servlet container. When you deploy a WAR to JBoss, it only performs the task of deploying the web application to the servlet container - depending on your distribution, the web application will be farmed off to Tomcat or Jetty or even Resin. The servlets, the JSPs and the static content will be handled by the embedded servlet container.

[vdreamer]

That still doesn't answer the question of why tomcat?
If jboss has a built in http server (JbossWEB , Jetty) then why tomcat?

[vdreamer]

That still doesn't answer the question of why tomcat?
If jboss has a built in http server (JbossWEB , Jetty) then why tomcat?

[jonlee]

So you have a choice of servlet containers. Tomcat is the Sun reference implementation, so you may want features that don't necessarily appear in Jetty. There is even a Resin plug-in if you want to have Resin as your embedded servlet container. Resin has persistent sessions, Tomcat has experimental persistent sessions and Jetty doesn't currently support persistent sessions - so the choices folks make are going to be based on their needs.

JBoss has as the standard JBossWEB install an embedded Jetty container.

As additional information, look at these measured performance characteristics that indicate some of the load variations between servlet container implementations: http://webperformanceinc.com/library/ServletReport/