Stefano Mazzocchi wrote:
> Sylvain Wallez wrote:
<snipped/>
>> This would lead to (adapted from Ilya's proposal) :
>>
>> <map:match pattern="*-*" name="mtch1">
>> <map:act type="my-action" name="act1">
>> <map:generate type="serverpages" src="{#mtch:1}.xsp">
>> <map:parameter name="display" value="{#mtch:2}"/>
>> <map:parameter name="param1" value="{#act1:1}"/>
>> <map:parameter name="param2" value="{#act1:2}"/>
>> <map:parameter name="param3" value="{request:1}"/>
>> <map:parameter name="param4" value="{1}"/>
>> </map:generate>
>> </map:act>
>> </map:match>
>>
>> Explanation :
>> - {#mtch1:xxx} come from statement named "mtch1"
>> - {#act1:xxx} come from statement named "act1"
>> - {request:xxx} come from input-module "request"
>> - {xxx} works as usual and gets its value from the enclosing statement.
>>
>> I changed "param-prefix" proposed by Ilya to "name" since this is
>> actually what it is : a name given to a sitemap statement.
>>
>> Thoughts ?
>
>
> know what? I like it. It seems a pretty nice solution and the use of
> anchor-like syntax is simple and understandable.
>
> So you get my +1 on this.
I don't know if the attribute should be called "name"? Isn't "id" the
right one for that? This would also ensure there are no duplicates in a
sitemap.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
