Thanks for all the responses!  We have a pluggable architecture where the topmost sitemap simply forwards on all requests to lower sitemaps (that it doesn't know about)  In a couple of cases, some of these lower sitemaps have things in common, but the topmost one can't really put all of these cases in there.  Looks like I am stuck with entities for now.  It would be cool to have common pipelines that could be "included"

Irv

On 11/30/05, Mark Lundquist <[EMAIL PROTECTED]> wrote:

On Nov 30, 2005, at 8:20 AM, Irv Salisbury wrote:

> I have two sitemaps that have some similar map:match and subsequent
> pipeline processing elements. Is there any "include" type element for
> a sitemap?
>
>  I cannot have a common parent sitemap and use a map:mount, so that
> option is out.
>
>  My only idea at this point is to use the dtd entity replacement type
> stuff that you can use on any xml file.
>
>  What I'd really like is something like:
>
>  <map:pipelines>
>   <map:include href="">>   <!-- Now add my own -->
>  </map:pipelines>
>
>  Any thoughts?

I'd really like to have that too, but unfortunately there's no such
thing.  In 2.2. there's a special include just for <map:components>,
but that won't do what we want.

I use XML entities, as you suggested.  The only real "gotcha" is that
if you change one of the included sitemap files, you have to "touch"
the topmost sitemap file (i.e. the one named in cocoon.xconf or in a
parent sitemap <mount>).

HTH,
—ml—


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]