On 1/31/06, Derek Harmel <[EMAIL PROTECTED]> wrote:
> > For Best Practice XMAP programming, there should be one and only one
> > match for a URL.  Use nesting when patterns will overlap:
>
> While this certainly makes sense, as you know, the original
> publication-sitemap.xmap does not follow your suggestion.  I'm a bit
> concerned that reworking that entire XMAP to follow your example would
> be very difficult, especially for someone new to Lenya like myself.

I agree the "default" example publication could be improved.  We'll do
it sometime.  You do not need to rewrite eveything to follow the
example, just move the one match (details below).

> > Processing continues through the matches (as if they were IF
> > statements) until the "return" statement: <map:serialize/>
>
> Then how come my first matching pipeline doesn't stop processing even
> though it contains a transform?  Now I'm even more confused ;)

A transform does not stop processing.  map:serialize is the normal
"return" statement.  See:
http://solprovider.com/lenya/nesting

> Thanks for the help solprovider.  I may consider what you suggested,
> but I have a deadline for this project, and it's becoming less and
> less realistic.  Right now, I'm looking for quick-and-dirty -- to be
> replaced with orderly-and-clean when I have the time.

Just copy/paste the pipelines so they nest properly.  Leave extra
whitespace so you can easily see the parts, and maybe comment the
parts.  Should take a less than two minutes to make the change and
test if it works as desired.

You need the section that starts:
      <map:match pattern="*/*/*/*/*/jobopenings/*.html">
to be directly after the line:
      <map:match pattern="**.html">

solprovider

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

Reply via email to