Return-Path: Delivered-To: apmail-forrest-user-archive@www.apache.org Received: (qmail 60187 invoked from network); 27 Jul 2004 05:28:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 27 Jul 2004 05:28:36 -0000 Received: (qmail 58549 invoked by uid 500); 27 Jul 2004 05:28:35 -0000 Delivered-To: apmail-forrest-user-archive@forrest.apache.org Received: (qmail 58521 invoked by uid 500); 27 Jul 2004 05:28:35 -0000 Mailing-List: contact user-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: user@forrest.apache.org Delivered-To: mailing list user@forrest.apache.org Received: (qmail 58510 invoked by uid 99); 27 Jul 2004 05:28:35 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [65.77.211.93] (HELO indexgeo.net) (65.77.211.93) by apache.org (qpsmtpd/0.27.1) with ESMTP; Mon, 26 Jul 2004 22:28:35 -0700 Received: from [192.168.1.100] (dsl-109.227.240.220.dsl.comindico.com.au [220.240.227.109]) (authenticated bits=0) by www2.kc.aoindustries.com (8.12.9-20030917/8.12.9) with ESMTP id i6R5SV3I029898 for ; Tue, 27 Jul 2004 00:28:32 -0500 Subject: Re: Cocoon App: Need Forrest-ation From: David Crossley To: user@forrest.apache.org In-Reply-To: <40F4DAAE.9010603@juntadeandalucia.es> References: <62C46C03B7AEFC448F5C80421919BB1D4291FF@ussas-mail01.amer.borl.net> <40F4DAAE.9010603@juntadeandalucia.es> Content-Type: text/plain Organization: Message-Id: <1090906098.1668.76565.camel@ighp> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 27 Jul 2004 15:28:19 +1000 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Thorsten Scherler wrote: > Howard Moore wrote: > >I've got several existing Cocoon applications. > > > >How can I bring the Forrest docs I have generated > >under my applications umbrella? > >Example; > >tomcat/webapps/cocoon/myapp/forrestdocs > > > >I've tried creating a static site but cocoon seems to > >have some problems with that. > > Can't you just use a reader for that! Should work like a charme! Howard, what "problems" are you referring to. Cocoon should be able to deal with any pre-prepared documents. As Thorsten has said, you would add some "match" statements to your cocoon/myapp/sitemap.xmap which deal with requests for forrestdocs/**.html and pdf and css by using However, this does sound clumsy doesn't it. You need to pre-generate the docs with Forrest then package them into your Cocoon application, or use other tricks, such as getting forrest to generate the static output straight into the Cocoon webapp directory after Cocoon has started. It sounds like what is really needed is a Cocoon Block called "forrest". We have talked about this before but not gone further. The block would contain all of the bit-and-pieces that forrest needs, such as sitemaps, skinconf, DTDs, the skin stylesheets, and the few extra jars. It should not need to supply any of the cocoon-related jars, which i think is the problem of "too much duplication" that you allude to below. > >Also a complete 'webapp' build has way too much > >cocoon duplication. > > > Do you want it in the same dir? Yeah that would not really work! > Why not /forrest war/ and just link to the forrest docu from your cocoon > site (2 independent site). Ok, you want to have it under your > application umbrella. > > ...then just copy the extracted war into > > tomcat/webapps/cocoon/myapp/forrestdocs > > and tell cocoon to mout the sitemap. You need 's/mout/mount/' of course. > >Can you kind and brilliant folks tell me how to do > >this? The easy way? :) > > I do not know whether that is the easy way, but it could be a way ;-) You are entering new territory here Howard. It is a place where we do want to go, however no-one has yet put in the energy. We would be pleased to hear how you go with some of those suggestions and what you think about the Cocoon block idea. -- David Crossley