Howdy, A couple of comments: 1. JBoss uses (or can use) Tomcat as its servlet/JSP container. We've used this setup in the past and like it. 2. If you need EJB support, or other J2EE features not offered by tomcat stand-alone, JBoss would be a good way to go. 3. While the initial thought behind tomcat was a pure reference implementation, at a time when none existed, I don't think this is the case now. It's still a reference implementation, used by Sun and JBoss etc. However, its performance is quite good, and it supports several key features above and beyond the spec.
Just my $.02, Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >Sent: Monday, November 25, 2002 8:52 AM >To: [EMAIL PROTECTED] >Subject: Tomcat or JBoss? > >I'm sure you get this question all the time, but this is not that type of >question. I've been using Tomcat for a while, like a year, in a production >environment. I think it's been doing fine so far. I've just got a new >server to replace my current application server that's been running Tomcat. >I was thinking maybe I should set this up with JBoss instead of Tomcat, >because this will be production. The reason I'm thinking about doing this >is one, because I'm at a stage where it would be easy to just install >whatever I want and two, I've read a couple places that Tomcat is just a >reference implementation. That it was not really designed to be in >production. It doesn't have to be just JBoss either. I just know a little >about it. Any suggestions would be great. > > >Thank You, > >Justin A. Stanczak >Web Manager >Shake Learning Resource Center >Vincennes University >(812)888-5813 > > > >-- >To unsubscribe, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:tomcat-user- >[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
