Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 20450 invoked from network); 12 Dec 2000 18:10:37 -0000 Received: from f259.law4.hotmail.com (HELO hotmail.com) (216.33.148.137) by locus.apache.org with SMTP; 12 Dec 2000 18:10:37 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 12 Dec 2000 10:10:06 -0800 Received: from 148.88.0.10 by lw4fd.law4.hotmail.msn.com with HTTP; Tue, 12 Dec 2000 18:10:06 GMT X-Originating-IP: [148.88.0.10] From: "Robin Green" To: cocoon-dev@xml.apache.org Subject: RE: XSPGenerator Date: Tue, 12 Dec 2000 18:10:06 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 12 Dec 2000 18:10:06.0384 (UTC) FILETIME=[C198EB00:01C06466] X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I don't see a problem with that. Just use util:include-uri (when it's ported to C2! ;) and Cocoon will catch the cocoon:// URI, or whatever is used to specify aggregation. This preserves separation of concerns - and requires virtually no new code for the XSP case, once you've coded general URI-based aggregation. That way you can even dynamically switch between internal and external aggregation because they are treated uniformly! "Torsten Curdt" wrote: >Guys, guys, guys... Still.. > >Will we then be able to control what to be aggregated >via XSP(!)? I think this important! (At least for me!) >-- >Torsten _____________________________________________________________________________________ Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com