Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 37146 invoked by uid 500); 13 Jul 2001 14:32:06 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 36996 invoked from network); 13 Jul 2001 14:31:44 -0000 From: "Anders Lindh" To: , Subject: RE: C1 to C2 Date: Fri, 13 Jul 2001 17:31:53 +0300 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3B4EE945.4E833AC1@sun1.oulu.fi> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Importance: Normal X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hmm. My guess is that you'd have to have matching patterns in the apache configuration, which isn't always possible and kinda sucks. - Anders -----Original Message----- From: juffer@sun3.oulu.fi [mailto:juffer@sun3.oulu.fi]On Behalf Of Andre Juffer Sent: 13. heinakuuta 2001 15:28 To: cocoon-users@xml.apache.org Subject: Re: C1 to C2 Anders Lindh wrote: > > >Be aware that C2 will serve _all_ the pages (including the static > >ones). If you are in an Apache+Tomcat+Cocoon context, this mean that > >Everything on your site will be served by C2. > > If you use apache you tell it what requests to pass to Tomcat (with mod_jk > or mod_jserv). You can e.g tell it to pass requests for all .xml files in > /cocoon to Tomcat (and cocoon if configured properly). This way all static > content can be served by apache (x100 faster) and all dynamic pages by > tomcat/cocoon. Yes, this is correct. This is the way I have done in the past (apache-tomcat-cocoon1). But is this going to work only if one uses the extension .xml., since Cocoon2 also uses patterns in its sitemap (e.g. "welcome" instead of "welcome.xml")? For tomcat-apache-cocoon1, the following is what I have in httpd.conf: LoadModule jserv_module libexec/mod_jserv.so ApJServManual on ApJServDefaultProtocol ajpv12 ApJServSecretKey DISABLED ApJServMountCopy on ApJServLogLevel notice ApJServDefaultHost localhost ApJServDefaultPort 8007 ApJServMount default /root AddType test/jsp .jsp AddHandler jserv-servlet .jsp AddType text/xml .xml AddHandler jserv-servlet .xml Alias /cocoon /usr/local/jakarta-tomcat-3.2.1/webapps/cocoon Options Indexes FollowSymLinks ApJServMount /cocoon /cocoon AddType text/xml .xml AddHandler jserv-servlet .xml AllowOverride None deny from all Alias /Foo /usr/local/jakarta-tomcat-3.2.1/webapps/Foo Options Indexes FollowSymLinks ApJServMount /Foo/servlet /Foo AllowOverride None deny from all The server.xml in tomcat/conf in fact includes an entry for cocoon1 as follows: org.apache.cocoon.Cocoon org.apache.cocoon.Cocoon properties cocoon.properties org.apache.cocoon.Cocoon *.xml > Everything that has the extension .xml including those in /Foo automatically is forwarded to cocoon1 and therefore served by cocoon1, while the static files are served by the Apache webserver. This all works very nicely. It must be possible to do the same thing with cocoon2 somehow, but it seems to me that these "patterns" could cause some problems. Andre. > - Anders > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: -- Andre H. Juffer | Phone: +358-8-553 1683 The Biocenter and | Fax: +358-8-553-1141 the Dep. of Biochemistry | Email: Andre.Juffer@oulu.fi University of Oulu, Finland | WWW: http://www.biochem.oulu.fi/research.html --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: