Sitemap wizards, I need a semantic question about tokenization in parameters answered.
Of the two following pipelines, which do you consider "correct"? I'm not asking how
it works today, I'm asking how it *should* work. It's a gray area.
The only token we care about is from the outside wildcard matcher, and all references
to a token are of this matcher:
<map:match pattern="xyz/*.html">
<map:act type="myAct">
<map:parameter name="arg1" value="foo/{../1}"/>
<map:generate src="{../1}"/>
...
</map:act>
</map:match>
---- or ----
<map:match pattern="xyz/*.html">
<map:act type="myAct">
<map:parameter name="arg1" value="foo/{1}"/>
<map:generate src="{../1}"/>
...
</map:act>
</map:match>
The difference is in the level that the parameter "arg1" is referenced from. It's a
parameter, so should it be referenced relative to the caller or relative to the child
parameters that it is embedded with.
Thanks,
-b
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
