Return-Path: 
 <cocoon-dev-return-18157-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 87328 invoked by uid 500); 29 Oct 2001 15:59:21 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 87309 invoked from network); 29 Oct 2001 15:59:20 -0000
From: "Torsten Curdt" <tcurdt@dff.st>
To: "Cocoon-Dev" <cocoon-dev@xml.apache.org>
Subject: cocoon:/ and content aggregation
Date: Mon, 29 Oct 2001 16:59:17 +0100
Message-ID: <CHEGLKNOIJHFNDNBCIAJEEKCCBAA.tcurdt@dff.st>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

AFAIK the cocoon: protocol has a scope of the current sitemap.
But I need to aggregate a resource from the parent sitemap.

Since it is also at the servlet context I tried:

        ...
        <map:aggregate element="page">
         <map:part src="context:/inRootSitemap.xml"/>
         <map:part src="cocoon:/inThisSitemapUri1.xsp"/>
         <map:part src="cocoon:/inThisSitemapUri2.xsp"/>
        </map:aggregate>
        ...

This did not work. Then I tried:

        ...
        <map:aggregate element="page">
         <map:part src="../inRootSitemap.xml"/>
         <map:part src="cocoon:/inThisSitemapUri1.xsp"/>
         <map:part src="cocoon:/inThisSitemapUri2.xsp"/>
        </map:aggregate>
        ...

This seems to work.
Then I figured out I could create a mapping in the
current sitemap with a generator grabbing the XML
file via the context: protocol. So it would be accessible
in the subsitemap:
        ...
        <map:aggregate element="page">
         <map:part src="cocoon:/inRootSitemap.xml"/>
         <map:part src="cocoon:/inThisSitemapUri1.xsp"/>
        ...

        <map:match pattern="inRootSitemap.xml">
         <map:generate src="context:/inRootSitemap.xml"/>
          ...

Now this leads to some questions:
1. Shouldn't the context: "protocol" also work at the
   src attribute of map:part?
2. Was is the expense of not using the cocoon: protocol
   at map:part?

Comments?
--
Torsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org