Return-Path: Delivered-To: apmail-forrest-user-archive@www.apache.org Received: (qmail 22803 invoked from network); 31 Jan 2005 23:41:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 31 Jan 2005 23:41:18 -0000 Received: (qmail 10908 invoked by uid 500); 31 Jan 2005 23:41:17 -0000 Delivered-To: apmail-forrest-user-archive@forrest.apache.org Received: (qmail 10879 invoked by uid 500); 31 Jan 2005 23:41:17 -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 10865 invoked by uid 99); 31 Jan 2005 23:41:17 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from atl104.trx.com (HELO atl104.trxfs.trx.com) (66.45.118.99) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 31 Jan 2005 15:41:15 -0800 Received: from trxatl100.mail.trx.com ([172.16.1.23]) by atl104.trxfs.trx.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 31 Jan 2005 18:41:13 -0500 content-class: urn:content-classes:message Subject: RE: Aggregation Example MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 31 Jan 2005 18:41:12 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: <322805D420B7D41180AE00508B5E25CD0B84CE0C@trxatl100.mail.trx.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Aggregation Example Thread-Index: AcUH3eLSmVhdeQGwQfS7VOEtb8n2/gADp8bw From: "Stefan Baramov" To: X-OriginalArrivalTime: 31 Jan 2005 23:41:13.0497 (UTC) FILETIME=[597E0890:01C507EE] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Okay, my real question is how to aggregate unknown number of documents? Here is my case (using Forrest 0.6): In my xdocs folder I have a folder = called tasks. It contains a collection of XML formatted files, where = each file describes a single task. I like to aggregate them all in one = single document "Task Summary". Here is what I have in site.xml file: --- site.xml --- Here the tasksummary.html points to a tasksummary.xml pipeline defined = in sitemap.xmap (It took me a significant time to figure out that a = pipeline is matched by its "pattern" instead of sort of ID) =09 where: task_header.xml is a generic header file.=20 footer.xml is a generic footer XML file The real problem is that in the teamtask2section pipeline I can specify = only one task file B001.teamtask. And I have multiple: B002, B003 and so = on. I tried wildcards such as :=20 But it does not work. So how do I aggregate unknown number of XML files = located in subdirectory of xdocs? Thanks Stefan=20 -----Original Message----- From: David Crossley [mailto:crossley@apache.org] Sent: Monday, January 31, 2005 4:43 PM To: user@forrest.apache.org Subject: Re: Aggregation Example Stefan Baramov wrote: > Can someone post a simple aggregation example. I've read the user mail = list, I've searched Forrest and Cocoon documentation on aggregation, and = I found very little information. It has to be simple but I can get it = right. I have no experience with Cocoon and I am getting lost.=20 >=20 > I would like to aggregate several XML files in a single one.=20 > How do I define my pipeline (in sitemap.xmap)?=20 > Or do I need multiple piplelines?=20 http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html#Aggregating http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html#Protocols There is an example in the Forrest core, but perhaps we should put a very basic example in the "forrest seed" site. You have not told us which version of forrest you are using. For the current trunk (i.e. 0.7-dev) see webapp/sitemap.xmap around line 490 and follow the aggregation where it gets its parts from other sitemap matches using the "cocoon:" protocol. > How do I link the generate document with site.xml? Aggregation is done in the sitemap.xmap ... that is nothing to do with site.xml ... We need an FAQ to reduce the confusion caused by the name site.xml --David