[ 
https://issues.apache.org/jira/browse/WW-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lukasz Lenart updated WW-3338:
------------------------------

    Description: 
According to http://struts.apache.org/2.1.8.1/docs/tag-syntax.html , any 
attribute value="" is interpreted for OGNL.

This is not true for {{<s:hidden ... value="myprop" />}} , which will use the 
literal string "myprop".

To get it to call my bean's getMyprop(), I need to say {{<s:hidden ... 
value="%{myprop}" />}}

Would be nice if this could be streamlined, so s:hidden conforms to the general 
principle.

As that change might break existing code, it might be more easily asked for 
than done.

  was:
According to http://struts.apache.org/2.1.8.1/docs/tag-syntax.html , any 
attribute value="" is interpreted for OGNL.

This is not true for <s:hidden ... value="myprop" /> , which will use the 
literal string "myprop".

To get it to call my bean's getMyprop(), I need to say <s:hidden ... 
value="%{myprop}" />

Would be nice if this could be streamlined, so s:hidden conforms to the general 
principle.

As that change might break existing code, it might be more easily asked for 
than done.


> <s:hidden> tag should interpret its value attribute same as the other tags do.
> ------------------------------------------------------------------------------
>
>                 Key: WW-3338
>                 URL: https://issues.apache.org/jira/browse/WW-3338
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Plugin - Tags
>    Affects Versions: 2.1.8
>            Reporter: Andreas Krüger
>             Fix For: 2.3.18
>
>
> According to http://struts.apache.org/2.1.8.1/docs/tag-syntax.html , any 
> attribute value="" is interpreted for OGNL.
> This is not true for {{<s:hidden ... value="myprop" />}} , which will use the 
> literal string "myprop".
> To get it to call my bean's getMyprop(), I need to say {{<s:hidden ... 
> value="%{myprop}" />}}
> Would be nice if this could be streamlined, so s:hidden conforms to the 
> general principle.
> As that change might break existing code, it might be more easily asked for 
> than done.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to