We already have XPath and it work well. I dont know why you need to change
this?
Antonio Gallardo.
El Miércoles, 09 de Octubre de 2002 15:27, Ilya A. Kriveshko escribió:
> Deeply respectable folks,
>
> I already posted on a similar issue (w/o response, thus far) but maybe
> that discussion was already dead by then. However, since my last message
> is relevant to this issue as well, I am taking the liberty to re-post it
> in this thread too:
>
> My previous post:
>
> How about prefixing of retuned parameters' names? Here's what I mean:
>
> <map:match pattern="*-*" param-prefix="mtch1">
> <!-- matcher returns parameters: '1' and '2', which are renamed to
> 'mtch1:1' and 'mtch1:2' -->
> <map:act type="my-action" param-prefix="act1">
> <!-- my-action alsoreturns parameters: '1' and '2', which are renamed
> to 'act1:1' and 'act1:2' -->
> <map:generate type="serverpages" src="{mtch:1}.xsp">
> <map:parameter name="display" value="{mtch1:2}"/>
> <map:parameter name="param1" value="{act1:1}"/>
> <map:parameter name="param2" value="{act1:2}"/>
> </map:generate>
> </map:act>
> </map:match>
>
> Obviously, the exact syntax (i.e. 'prefix:name') is not crucial here.
>
> The sitemap components themselves would not be aware of the prefix, and
> would simply return a Map with "1" and "2".
> The prefix would be prepended to all the parameter names in that Map by
> whatever code is interpreting/executing the sitemap (?)
> This way one can always control the visibility of the parameters in
> nested elements explicitly by choosing a unique prefix or a matching
> prefix. This would also not require any changes to the existing users'
> sitemaps, since w/o prefixes everything would work as it does now.
>
> All that would be needed, is a change to:
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.jav
>a's invokeNodes() method to pre-pend the prefixes to the keys in the
> currentMap.
>
> If my proposition is acceptable to you, I am even willing to implement
> it ('cause it's short and easy).
>
> Sorry for intruding on your debate, but I have contributed my opinions
> and code here in the past and have been welcome then.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
