No you can not have those two subsequent map:mount under one
map:match, as you know the processing is sequential.  Once the
matcher is matched you have moved to the 1st mount location. 
However you can have another sub-mount relative to the 1st
sub-mount directory, and in each sub-mount dir you just have to
have a map:mount in its respective sitemap.xmap.  I dont believe
it can walk back the tree easily like you have it laid out. 

If you are wanting to mount to different location dependent on
the url, then you need a different matcher pattern and map:mount
  pair. Look at the main sitemap.xmap on how each mount is
directed, they have separate matcher for each. I hope this
helps.

enio 
--- Tim Olson <[EMAIL PROTECTED]> wrote:
> it seems that trying to mount more than one sitemap per
> request only mounts
> the first one.  in the following example:
>  
>     <map:match pattern="*/*/*"> <!-- domain/page/action -->
> 
>       <!-- mount root sitemap -->
>       <map:mount check-reload="yes" src="c:/mag/xsl/root.xmap"
> uri-prefix=""/>
>       <!-- mount domain-specific sitemap -->
>       <map:mount check-reload="yes"
> src="c:/mag/xsl/{1}/{2}.xmap"
> uri-prefix="{1}/{2}"/>
>  
>       <map:aggregate element="data">
>         <!-- <map:part src="configuration.xml"/> -->
>         <map:part src="cocoon://{1}/{2}/{3}"/>
>       </map:aggregate>
>       <map:call resource="respond"/>
> 
>     </map:match>
>  
> the request works if the pattern is matched by the 1st sitemap
> (root.xmap)
> but "Resource Not Found" is given for all URLs handled by the
> second
> sitemap.  some pages are the same for all our clients and
> should be handled
> in the root.xmap but some pages are customized per domain. 
> any ideas how to
> pull this off?
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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

Reply via email to