Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 36085 invoked from network); 16 Mar 2004 03:57:21 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 16 Mar 2004 03:57:21 -0000 Received: (qmail 73294 invoked by uid 500); 16 Mar 2004 03:56:53 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 73277 invoked by uid 500); 16 Mar 2004 03:56:53 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 73263 invoked from network); 16 Mar 2004 03:56:53 -0000 Received: from unknown (HELO terror.vuw.ac.nz) (130.195.86.21) by daedalus.apache.org with SMTP; 16 Mar 2004 03:56:53 -0000 Received: from [130.195.85.188] (HELO coso.staff.vuw.ac.nz) by terror.vuw.ac.nz (CommuniGate Pro SMTP 3.5.9) with ESMTP id 1714680 for users@cocoon.apache.org; Tue, 16 Mar 2004 17:02:53 +1300 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: Recursive Pipeline Date: Tue, 16 Mar 2004 16:57:02 +1300 Message-ID: <5744FAECB4B8864F83CB05F2E1D16EEBBAA344@coso.staff.vuw.ac.nz> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Recursive Pipeline Thread-Index: AcQGuWwAj0XlXqI1Rdmedh/Z9UQI9AET5G6QAAAqkYA= From: "Conal Tuohy" To: 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 Ack! Fingers slipped! Here's what I meant to write: > I did something like this once, to aggregate a list of html=20 > pages together. Each page had a [next] link at the bottom,=20 > and my pipeline basically followed these links. I think you=20 > want something similar. I don't have the code still, but from=20 > memory, something like this: >=20 Call the pipeline first with "page/1".=20 The XSL check-if-found-or-keep-looking.xsl should check if the record is = in the page: if so it should return the contents of the page (i.e. an = identity transform). If not found, it should return only an xinclude = statement. So the entire output document would be just the single = element: Then the xinclude transformer handles the rest. If the record was found = then the xinclude transformer does nothing, and the page is serialized. = If the record was not found then the xinclude transformer will make the = recursive sitemap call. Cheers Con --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org