Well this has not been my experience. My first attempt at Tomcat, I had the server up and running and executing My JSP files within an hour, not sample JSP's.
-----Original Message----- From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]] Sent: Monday, April 08, 2002 10:45 AM To: Tomcat Users List Subject: AW: NIGHTMARE That's a bit unfair. What you say is just the easy part: Running tomcat stand alone and just using the examples and the manager. There are several problems that can make the installation of tomcat quite difficult. - The documentation is quite confusing. You have to read many documents to get startet and find out how to achieve certain goals. (All this howto's are nice, but you already have to know something to find out, which howto will help you to solve a given problem.) For some documents you need more knowledge than you need write and run simple php skripts. (e.g. Classloader-How-To) Just some little examples (There are more): Connectors: There are two connectors: mod_webapp and mod_jk For a beginner it is very difficult to find out which one to use and what's the difference between them. Both connectors have their pitfalls where you can easily get stuck. It can be hard to find out which one is suitable for the IIS integration if you don't have enough patience. (The introduction just talkes about apache, not iis, not netscape) It would be better to extend the introduction in http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/ajp.htmlwith with an enumeration which servers are supported and add some links to the part where the integration to each server is described. The Howto is not well organized, the terminology is explained in the apache howto. That's not where I would look if I would want to integrate with IIS (which I won't). Download Page: If you go to the download page http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/bin/ there are many file listed. There is no hint what to to with this files, what's the difference between *.exe, *.exe.asc, *.zip, *.tar.gz, *.tar.gz.asc. (The document RUNNING.TXT that is referenced elsewhere on the site just talks about how to install a nighly binary from a zip that has a different name than the existing files) that not a problem for someone who is not doing things like this for the first time, but for a beginner it's at least confusing.) Some subtle problems in the servlet spec: Tell me what's wrong about this (and where can I find a document that explains that): <welcome-file-list> <welcome-file>/jsp/index.jsp</welcome-file> </welcome-file-list> (Tell me what happens. Read as much documentation or specification as you like, but don't look at the tomcat source or try it) or <welcome-file-list> <welcome-file>jsp/index.jsp?Action=Start</welcome-file> </welcome-file-list> (Again) One thing at last: As a servlet engine and jsp container tomcat offers much more than PHP can offer. But at the price that simple things can be more complicated than in other script languages. Currently I have the feeling that some simple things are more complicated than neccesary. (Some of them are more a result of the spec than just a tomcat problem.) > -----Ursprüngliche Nachricht----- > Von: Timlin, Bob [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 8. April 2002 18:31 > An: Tomcat Users List > Betreff: RE: NIGHTMARE <snip/> > Well in a Unix or Linux environment that is all you have to do. In a > Windows environment that will get Tomcat running in a DOS > window. To run as an NT Service there are more steps involved. -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
