Hey 

I agree with what pete said, for a free product Tomcat
is better than most of the servlet containers. AS for
the documentation goes, yes agree its a bit scanty but
look at the help you get from fellow developers like
us when you post a distress request, do u see such
kind of support anywere else? true you dont get online
telephone support or something like that , but I think
the mailing list is one of the very largely subscribed
to. 

As pete suggested may be you can try to figure out
your problem and then post your solution so that
others benefit, that is the spirit of open source. 

Have a good day , if you dont like tomcat u r free to
try JRUN or weblogic or websphere or Iplanet.. resin 

Goodluck

Kris




--- pete <[EMAIL PROTECTED]> wrote:
> 
> If there is a lack of documentation, that is par for
> the course with any 
> project that doesn't have paid technical writers. I
> don't recall seeing 
> a big sign on the front of jakarta.apache.org saying
> 'Get your complete 
> and comprehensive documentation here'.
> 
> If you wanted to, you could probably hire someone
> from this list to 
> write up a good configuration guide for tomcat, for
> less than the price 
> of a WebLogic license. Maybe you could think about
> that. You would then 
> have both solved your problem, contributed in a
> meaningful way to the 
> community and helped a fellow tomcat user
> financially, instead of 
> finding, 6 months down the track, that tomcat
> outperforms, is more 
> stable and a lot cheaper than WebLogic, yet still
> has no good docs.
> 
> Your comment about mod_jk is just wrong. Exactly how
> does it slow down 
> your web server by 1000%? I imagine if you are using
> servlets heavily, 
> and this results in max CPU usage or something, then
> apache will 
> struggle to serve requests, but this situation would
> be no different if 
> you ran tomcat standalone, or if you switched to
> another servlet engine.
> 
> If your virtual hosts have different servlet
> mappings? well, worst case 
> scenario you could write a perl or shell script, or
> better still a GUI 
> or servlet-based Java app that automated these
> configuration chores. You 
> know what you could then do? You could contribute it
> back to the project 
> so that other people can use it to save time.
> 
> And if you have a problem no-one has experienced
> before, and posting to 
> the mailing list doesn't elicit a reply? I suppose
> these commercial 
> servlet engines are all 100% bugless, trouble free,
> and have perfect 
> tchnical support. Of course nobody has problems with
> these servlet 
> engines, which is why the Resin, JRun and WebLogic
> mailing lists are 
> completely empty, and you can't find a single link
> on google when you 
> type 'resin problem' or 'weblogic problem' into it.
> 
> If Tomcat does not fit your needs, or you are unable
> to configure it 
> correctly, by all means, ask for help. But don't
> claim it SUCKs just 
> because you can't solve your own problems, or phrase
> your questions in 
> such an obnoxious manner that help is unlikely to be
> willingly provided.
> 
> 
> 
> -Pete
> 
> > Hi guys,
> > 
> > I really think that TOMCAT SUCKS so bad. I'm not
> against the open source 
> > community but this is why I think that TOMCAT
> sucks:
> > 
> > 1. The documentation for Tomcat is so bad and it
> covers only the basic 
> > server installation. HELLOOOO - usually for
> production purposes people have 
> > load balancers, virtual hosts, etc.2. Virtual
> hosting for Tomcat is almost impossible - especially
> if you have a 
> > load balancer in front of the web server. 
> > 
> > 3. The integration with apache (using mod_jk)
> sucks. It slows down the 
> > productivity of the web server with at least 1000%
> > 
> > 4. And guess what is the hell you have to go
> through if your virtual hosts 
> > have different servlets mappings. You waste time
> and you know - time is money.
> > 
> > 5. And what if you have a problem that is not in
> the documentation (99% of 
> > the problem with Tomcat are not even mentioned in
> the documentation)? I guess 
> > the only way is to post in the mailing list. And
> guess what happens if nobody 
> > has experienced this problem before? You have to
> start wasting your time 
> > again.
> > 
> > I really think that TOMCAT is OK for testing
> purposes. Trust me - for complex 
> > configurations it sucks. 
> > If you want to use a good production application
> server - take a look at 
> > WebLogic, Resin, Allaire JRun, etc.
> > 
> > Nick
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

Reply via email to