I agree; though I haven't worked with any recent versions of JBoss, I
know Tomcat can perform well and is frequently updated. That it's open
source is another grand plus, given the range of customization access to
source provides (this, in addition to tomcat's flexible configuration
options).
It's also notable that Tomcat is *extremely* unlikely to become a
strictly commercial product or require future (monetary)
investment.
-Steve
At 09:42 AM 6/25/2003, Morgan, Todd wrote:
Seems
to me that the best solution is to go to Tomcat. JBoss is overkill
if you are only needing a servlet container. As a matter of fact,
there is a JBoss distribution that uses Tomcat as its servlet container.
(There's another that uses Jetty).
TJ
- -----Original Message-----
- From: Jeremy Louis
[mailto:jeremy.louis@xxxxxxxx]
- Sent: Wednesday, June 25, 2003 10:30 AM
- To: users@xxxxxxxxxx
- Subject: Re: [cinjug-users] Re: Servlet Container Debate
- I agree. Also if you can't have any down time you can cluster a
couple of servers with Jboss and almost eliminate any down time.
-
- COJUG wrote:
- JBoss
(www.jboss.org) - Free, Open Source,
fast development and easy deployment. If nothing else I would say start
here. If your applications adheres to the specification it should be easy
to migrate to a commercial product if JBoss does not meet your
needs. -----------------------------------------------
- Christopher M. Judd
- Judd Solutions, LLC
- President & Consultant 685 Farrington Dr.
- Worthington, OH 43085
- phone: 614-378-4119
- email:
cjudd@xxxxxxxxxxxxxxxxx
- web:
www.juddsolutions.com
- ----- Original Message -----
- From: John Olmstead
- To: users@xxxxxxxxxx
- Sent: Wednesday, June 25, 2003 9:35 AM
- Subject: Servlet Container Debate
- Gentlemen; We are considering upgrading our servlet container
to one that supports the 2.3 servlet api and jsp 1.2 api (Yes, I know we
are in the dark ages!). We are running JRun 3.1 in production and
are running our applications on a development server (JRun 4.0)
with 128 bit ssl encryption implemented, and the application server takes
about 7 -10 minutes to come back after a restart. I don't think this will
be tolerated on a production server. I also have some concern that
there will be no $$ for training on a new servlet container, so I'll be
on my own to implement, administer and support a much more sophisticated
container than what I am working with now. 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. Thanks; John
OlmsteaddbaDirect
|