Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 6531 invoked from network); 15 Aug 2002 09:12:39 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 15 Aug 2002 09:12:39 -0000 Received: (qmail 25318 invoked by uid 97); 15 Aug 2002 09:12:50 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 25301 invoked by uid 97); 15 Aug 2002 09:12:49 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 25285 invoked by uid 98); 15 Aug 2002 09:12:48 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <0101DE8C7BB0D211BD480020AFBFE4E9253DFF@cludo> From: John Burgess To: Tomcat Users List Subject: RE: Getting mod_webapp - should I give up? Date: Thu, 15 Aug 2002 10:16:16 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1252" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N As far as I can see, mod_webapp was designed to be an easier to setup way of integrating apache and tomcat and it succeeds in this on windows for apache 1.3 and tomcat 4.0x. However, it will serve all content from a directory you configure it for from tomcat whereas mod_jk* will leave html, jpg, gif etc to Apache. The way round this is to have your pics and static pages in a different location that is served by Apache alone and referenced as /static/xxx or similar but this then loses the convenience of a single war file containing everything needed for the application (it can even include a mod_jk conf file which can help with mapping servlets without the need for the ugly /servlet/servlet_name of the auto-created jk conf filers of tomcat 3) Worse than the above, I have found that large requests or frequent requests or just at random cause tomcat to give an error about the client terminating or some such and hang. With mod_jk this doesn't happen (or with tomcat standalone). Best Wishes John Burgess john@riskdecisions.com Tel: 01865 718666 Fax: 01865 718600 -----Original Message----- From: Murray Cumming [mailto:murrayc@usa.net] Sent: Thursday, August 15, 2002 10:04 AM To: Murray Cumming Cc: Tomcat-User Subject: Getting mod_webapp - should I give up? So, nobody can help me to build mod_webapp, and there is no rpm of it to download. Does this just mean that it can't be built? I don't remember where I read that mod_webapp was the "correct" way to integrate Apache2 and Tomcat4. The documentation is a bit fragmented. Is mod_jk* the true way to do this? If so, could someone give me a URL to a definitive page that says this and how to get/build it? I just want to integrate Apache2 and tomcat4, not do anything special. About a year ago I did successfully integrate Apache1 and tomcat, but I haven't worked with tomcat since then. On Tue, 2002-08-13 at 17:20, Murray Cumming wrote: > OK, so if I had read README.txt properly then I would know that I need > to do a cvs checkout of apr into the webapp directory. > > It tells me to copy and modify a build.properties.sample file, but there > is no such file there, so I ignored that. > > As instructed, I then ran > support/buildConf.sh > > This creates a configure script, which I am tempted to run, but the next > step tells me to run ant. I did that, and I still this error: > > BUILD FAILED > file:/home/murrayc/jakarta-tomcat-connectors-4.0.4-src/webapp/build.xml:105: Cannot find Tomcat 4.0 classes > > So, how do I tell it where to find these tomcat classes? I have already > installed jakarta-tomcat-4 from here: > http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4/rpms/ -- Murray Cumming murrayc@usa.net www.murrayc.com -- To unsubscribe, e-mail: For additional commands, e-mail: --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.380 / Virus Database: 213 - Release Date: 24/07/02 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.380 / Virus Database: 213 - Release Date: 24/07/02 -- To unsubscribe, e-mail: For additional commands, e-mail: