cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COCOON-2110) Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine
Date Sat, 11 Aug 2007 01:47:42 GMT

    [ https://issues.apache.org/jira/browse/COCOON-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519184
] 

Vadim Gritsenko commented on COCOON-2110:
-----------------------------------------

Don't we have a history of using #{foo} for jxpath and ${foo} for jexl? Doing it differently
would just result in more confusion. I'd rather have it more uniform throughout.

> Evaluate expressions defined in cocooon-expression-language-api in Sitemap engine
> ---------------------------------------------------------------------------------
>
>                 Key: COCOON-2110
>                 URL: https://issues.apache.org/jira/browse/COCOON-2110
>             Project: Cocoon
>          Issue Type: New Feature
>          Components: - Components: Sitemap, - Expression language
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Grzegorz Kossakowski
>            Assignee: Grzegorz Kossakowski
>             Fix For: 2.2-dev (Current SVN)
>
>
> Description of the task is relatively simple; all I want to achieve is to make possible
following construct in sitemap:
> <map:transform type="xslt">
>   <map:parameter name="request_param" value="${cocoon/request/some_param}"/>
> </map:transform>
> assuming that JXPath (used above) is default EL of choice. Of course one would be able
to use following construct:
> <map:transform type="xslt">
>   <map:parameter name="request_param" value="${jexl:cocoon.request.some_param}"/>
> </map:transform>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message