Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 60161 invoked from network); 12 Dec 2003 00:34:56 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 12 Dec 2003 00:34:56 -0000 Received: (qmail 78834 invoked by uid 500); 12 Dec 2003 00:34:39 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 78802 invoked by uid 500); 12 Dec 2003 00:34:39 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 78781 invoked from network); 12 Dec 2003 00:34:39 -0000 Received: from unknown (HELO server1.livestoryboard.com) (209.61.132.12) by daedalus.apache.org with SMTP; 12 Dec 2003 00:34:39 -0000 Received: from koberg.com (livestoryboard.com [209.61.132.12] (may be forged)) (authenticated) by server1.livestoryboard.com (8.11.6/8.11.6) with ESMTP id hBC0a2b05099 for ; Thu, 11 Dec 2003 18:36:02 -0600 Message-ID: <3FD90CAD.8060908@koberg.com> Date: Thu, 11 Dec 2003 16:32:45 -0800 From: Robert Koberg User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: overriding part of a skin References: <3FD8A755.80309@wkwyw.net> <3FD8B20C.9000406@koberg.com> <1071181715.1236.33470.camel@ighp> <3FD8F4BE.9060307@koberg.com> <1071186319.1237.33824.camel@ighp> In-Reply-To: <1071186319.1237.33824.camel@ighp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hey, David Crossley wrote: > Robert Koberg wrote: > >>David Crossley wrote: >> >>>Robert Koberg wrote: > > > >>>Good idea Robert. I have always wanted to try using the >>>Catalog Entity Resolver for other tasks. >>> >>>Do you have an example of how to implement it? > > >>If we are talking about Ant's xmlcatalog (as opposed to >>the xml-common's catalog resolver, right?), ... > > > They are one and the same. I would love it if you could tell me how I could use Ant's xmlcatalog interchangeably with the xml commons catalog or vice versa. > The Ant xmlcatalog task > allows us to use it at build-time. Also the Ant xmlcatalog > can refer to Forrest's default catalog.xcat file for all > the standard mapping to DTDs and stuff. > > >>then something like this would do it: >>... >> >> > location="${my.forrest.xsl}/document2html.xsl"/> >> > location="${my.forrest.xsl}/foo.xsl"/> >> > location="${my.forrest.config}/boo.xml"/> >> >>... >> >>then use your xslt task like so: >>... >> >> >> >>... >> >>It would be somewhat similar if not using ant for transforms >>and using the standard xml-commons catalog resolver (I will >>provide an example if needed). I have not been following forrest >>too closely as the site.xml, so if this does not work just say so. > > > This is the problem. Skins are assembled by the sitemap and not > by an Ant task, so that happens via Cocoon at forrest run-time. > Therefore we would need to declare the mappings in > src/core/context/resources/schema/catalog.xcat > and use the main entity resolver. OK. There is a point when the child must leave the nest and fly off on their own. It must be the holiday season.., but I see forrest is to cocoon like the child is to their mother. At some point interests and needs diverge. (I am kinda waiting...) best, -Rob > > However, configurable paths to the XSLs are the issue. I suppose > that we could dynamically generate an additional catalog.xcat at > build-time and reference that from the main one. > > --David > >