>From: "Mike DiChiappari" <[EMAIL PROTECTED]> >To: "Tomcat Users List" <[EMAIL PROTECTED]> >Sent: Monday, December 09, 2002 6:37 PM >Subject: RE: I don�t understand the objective of this open list ! > > >Notice that I didn't ask a question JOEL BERGMAN (are you a Jakarta >developer). I simply chimed in when someone else expressed >dissatisfaction with this list. I have been disappointed and >frustrated by the **** that is called documentation. I stopped >trying to get tomcat to work properly over a year ago. Recently I >looked into it again, and noticed little to no improvement.
Amazingly, many of us using the same Tomcat binaries and documentation have had little or no trouble doing all kinds of things with Tomcat. Have you considered that the lowest common denominator in your problems could be you? Granted, my first impression was that Tomcat had too high of a learning curve. However, after actually looking at the examples, the documentation, and experimenting with it, I've actually found it fairly straightforward. The difference is that I work through whatever problems I encounter rather than citing the software as the problem. In the process, I'm learning the "in's and out's" of Tomcat and finding it's much simpler than I initial believed. That doesn't mean everything I try works the first time, but that's the reality of any app server. >Note that my background is technical, with over twenty years of >building commercial quality software. I don't believe in a lot of >pie-in-the-sky ideals in terms of software development. I rate >software on three important criteria: does it do what it is intended, >can it be used easily, and is it maintainable. > >In terms of tomcat, I give it a grade of incomplete on all three of >the above. I can not tell if it does what its supposed to because I >can't get it to work with a reasonable amount of effort. I think you're grading Tomcat on criteria that aren't necessarily applicable. Tomcat is the servlet container that is the official reference implementation for the Servlet/JSP spec. It's the proof-of-concept that the specs are implementable. I believe there is a test suite that is used to verify this; it's not based on whether or not you personally can tell if it does this. On the other hand, I'd still disagree with all three of your assessments. I think that demonstrates that we've all had varying degrees of difficulty or ease in working with the same software and documentation. While some may find the documentation lacking, others might find it overkill. >Here if my contribution to Jarkata and people looking for a low cost >Java solution. Use JRUN (discalimer: I am not affiliated with >Macromedia in any way). It is under $1000 and includes a full J2EE >implementation (JSP, servlets, EJB). It looks like the installer >does all the stuff that mod_jk, mod_jk2, and mod_web are supposed to >(if anyone could get them to work). A development version is >available for free. > >Mike Sun also has released a free J2EE server (Sun ONE Platform Edition) which I've spent some significant time with since it was released early-access. It has documentation and a nice administrative interface, etc. However, this does not necessarily equate to strong usability. I could not get the ISAPI filter to work with Sun ONE for anything, but in Tomcat it took me about five minutes. I've also used Resin and JRun, and they each have their strengths and weaknesses. They're all subject to the same constraints as about any other app server: they can't think or learn for you. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
