I have a file structure serving two sites with the same XML data, but
with different XSLTs for layout:
/cocoon/ <-- Tomcat's application path
/cocoon/k8 <--- the main site
/cocoon/k8/xml <--- XML files
/cocoon/k8/alexander <--- first site's XSLTs and CSSs etc...
/cocoon/k8/moritz <--- second site's XSLTs and CSSs etc...
Now I just modified the sample sitemap to mount the new sitemap in
/cocoon/k8:
<map:pipeline>
<map:match pattern="k8/**">
<map:mount check-reload="yes" src="k8/sitemap.xmap" uri-prefix="k8"/>
</map:match>
</map:pipeline>
Inside the k8/sitemap.xmap I mount the two other sitemaps for the two
sites (why do I have to use k8/moritz/sitemap.xmap instead of just
moritz/sitemap.xmap here?):
<map:match pattern="moritz/**">
<map:mount check-reload="yes" src="k8/moritz/sitemap.xmap"
uri-prefix="moritz"/>
</map:match>
<map:match pattern="alexander/**">
<map:mount check-reload="yes" src="k8/alexander/sitemap.xmap"
uri-prefix="alexander"/>
</map:match>
And finally I construct my HTML pages this way:
<map:match pattern="projects/*.html">
<map:aggregate element="page">
<map:part src="menu.xml"/> <-- menu.xml is in /cocoon/k8/alexander
<map:part src="k8/xml/projects/{1}.xml"/> <-- .xml is in /cocoon/k8/xml
</map:aggregate>
<map:transform src="project.xsl"> <-- project.xsl is in
/cocoon/k8/alexander
<map:parameter name="menu_main" value="projects"/>
<map:parameter name="menu_sub" value="{1}"/>
<map:parameter name="path" value="projects"/>
</map:transform>
<map:serialize type="html"/>
</map:match>
I always get a resource not found (so I think my paths are wrong). I
also have to always refresh the sitemap in /cocoon/k8 to get Cocoon to
reload the sitemaps in /cocoon/k8/alexander (at least it seems to me).
What am I doing wrong? How do I get some root-relative paths? I tried
cocoon:// and context:// and also /...
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
- RE: Problems resolving internal paths Alexander Czernay
- RE: Problems resolving internal paths Reinhard Poetz
- Re: Problems resolving internal paths Alexander Czernay
- Re: Problems resolving internal paths Timothy Larson
- Re: Problems resolving internal paths Timothy Larson