On 09.06.2004 18:47, Terry Brick wrote:
b) The example I put in my first email also had "{../../locale}". This is also not
covered in
this document. My assumption is that it is reference to a URL parameter that has been
submitted?
No, it refers to an action that returned a locale parameter to the sitemap. As the snippet you posted does not have two levels up, it must be somewhere outside the resource.
For things like URL parameters (and many more) there are additional input modules. The syntax would be for example {request-param:myparam}.
c) And finally, either I don't understand one example in the Wiki document or there is a mistake.... It states, "So if you insert a new level e.g. by calling an action or a matcher. You have to refer the previous level to get the same value from the Matcher." ... it then gives this example ... <map:match pattern="images/*.gif"> <map:act type="resource-exists"> <map:parameter name="url" value="resources/images/{1}.gif"> <!-- new level --> <map:read src="resources/images/{../1}.gif" mime-type="images/gif"/> </map:act> </map:match> ...
Conceptually (not literally) shouldn't it be something like?.... <map:match pattern="images/*.gif"> {1}
{1} refers to the asterisk above.
<!-- new level -->
<map:act>
{../1}
In the sample {1} is used in a map:parameter belonging to the action. It's still not in the scope of the action, but in the scope of the matcher, so it's still {1}.
<!-- new level -->
<map:read>
{../../1}
map:read does not change the scope, so it's still the action's scope. That means {../1}
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
