i play arround and forced the strange behaviour in annother way:
i tested the follwing scenario:
the Base-Sitemap:
<base-sitemap>
<!-- mounted subapplication -->
<map:match pattern="sub/**">
<map:mount check-reload="yes" src="sub/sitemap.xmap" uri-prefix="sub"/>
</map:match>
<map:match pattern="test">
<map:generate src="cocoon:/sub/content"/>
<map:transform/>
...
<map:transform/>
<map:serialize type="xml"/>
</map:match>
</base-sitemap>
the SubSitemap :
<sub-sitemap>
<map:match pattern="*.xml">
<map:generate src="xsp/{1}.xml" type="serverpages"/>
<map:serialize type="xml"/>
</map:match>
<map:match pattern="content">
<map:aggregate element="subpage">
<map:part src="cocoon:/header.xml" element="header"/>
<map:part src="cocoon:/footer.xml" element="footer"/>
</map:aggregate>
<map:serialize type="xml"/>
</map:match>
</subsitemap>
this gives an error. it seems that cocoon tries to find the correspondig
matches for "header.xml" and
"footer.xml" in the base-sitemap and not in the sub-sitemap.
--
Frank
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
