On 2/9/06, Derek Harmel <[EMAIL PROTECTED]> wrote:
> Just gave this a try and still no luck. Instead of getting a Cocoon
> error, I now get the standard Lenya 404 page, saying "The requested
> document '' with document-id '' does not exist."
>
> Which, again, I do not understand as there is a pipeline that matches,
> transforms, and serializes. As I've complained about in a different
> thread, I don't understand why I'm entering into the main entry
> pipeline in publication-sitemap.xmap if I'm catching the URL in a
> pipeline above it and serializing. Too many xmaps for a newbie to
> decipher...and follow.
I documented this problem on my "Nesting" page. For best results,
make certain there is one and only one pipeline for a given request in
an XMAP. Usually this means:
<map:match pattern="**">
<map:match pattern="**.html">
<map:match pattern="*/something/*.html">
<!-- Special Case -->
</map:match>
<!-- Default HTML -->
</map:match>
<!-- Default (Not HTML) -->
</map:match>
The results are unpredictable if you have (in any order):
<map:match pattern="*/something/*.html">
</map:match>
<map:match pattern="**.html">
</map:match>
Sometimes it runs both; sometimes it runs the wrong one. It never
seems to run the one you want.
An alternative to nesting is to avoid the "**.html" match, either by
- using a different match (usually by changing the extension),
- using a Usecase to completely avoid publication-sitemap.xmap. (Good
for clean code)
- both use a different match and keep the code clean:
<map:match pattern="**.myextension">
<map:mount uri-prefix="" src="myxmap.xmap"/>
</map:match>
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
