[
https://issues.apache.org/jira/browse/COCOON-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519193
]
Jörg Heinicke commented on COCOON-2110:
---------------------------------------
I neither can recall it. How this one came up, Grek? I'm in favor of it though.
Backward incompatible change itself seems not to be disqualifying, see the
discussion about the environment. One can argue with public vs. private API
here though ...
In this case it should be even possible to support the #{} expressions as well
and log some deprecation message. This would allow a change in 2.2.
Let's bring it back to dev list - even if it's only for the decision of
changing the start chars.
> 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.
