Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 68054 invoked by uid 500); 3 Jul 2001 09:11:15 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 67940 invoked from network); 3 Jul 2001 09:11:09 -0000 To: cocoon-dev@xml.apache.org Subject: Re: AW: Sitemap/subsitemap Message-ID: <994151465.3b418c2974abd@mail.otego.com> Date: Tue, 03 Jul 2001 11:11:05 +0200 (CEST) From: Giacomo Pati References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.4 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Quoting Carsten Ziegeler : > > Giacomo Pati wrote: > > > > On Mon, 2 Jul 2001, DZIEMBOWSKI,KINGA (HP-NewJersey,ex2) wrote: > > > > > Hi, > > > I need to understand the capabilities and limitations of > > sitemap/subsitemap. > > > Is there any documentation describing the sitemap/subsitemap design, > > > assumptions and usage? If it does not exist - is it possible to ask > the > > > person who designed that behavior to put together the doc > > similar to "docs: > > > draft on matchers and selectors" just to have all the ideas, > > capabilities > > > and limitations in one place? ( I know that I can figure out it from > the > > > code - but it is time consuming and not always clearly showing all > > > capabilities and limitations). > > > > > > The second question is: > > > we have Generators which - generate > > > Transformers which - transform > > > Matchers which - match > > > Selectors which - select > > > Actions which - act > > > ?? which - aggregate > > > > > > It is a pattern that the components used in the system are > > "declared" in the > > > sitemap before they are used as a part of pipeline definition. > > > Why the aggregation is not following the pattern? > > > > Yes, it is true for components but aggregation is not componentized. > > You will have noticed that there isn't a Mounter as well :) > > > Not to forget the hard coded ErrorGenerator... Are you trying to give a hint to us ;) (componentizing error-handlers?) Isn't a standard DTD/Schema enought for errors? Giacomo --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org