John Olmstead wrote:
I know we have beat the IDE issue to death, but I don't believe we
have had the servlet container debate. Could I ask this esteemed
group to weigh in on issues like support, ease of implementation,
compliance with J2EE specification, scalability and reliability for
whatever your favorite happens to be? We run Win 2k on our servlet
container, which runs stand alone (not connected to iis) with a
sqlserver 2000 backend.
We tend to use Resin (2.1.6 at the moment), which is at
http://www.caucho.com/. It's free for development but not for
deployment. It has been much faster and more robust for us than Tomcat,
although Tomcat has definitely been getting better in recent releases
(e.g. 4.1+). We do also use Tomcat, though, especially to test
compliance with the servlet spec. If you need EJBs and/or clustering,
as many folks have said, you're well advised to go with JBoss.
However, the best thing to do is to design your app so that it is
J2EE-compliant (e.g. develop using Tomcat, which is fairly "strict"),
and then you can change out your servlet container pretty much at whim.
For example, we had developed this one particular app for a good few
months using Resin. We built the war, deployed to Tomcat, found two
problems (both in web.xml, by the way), and then it worked on both.
- Eric
|