[
https://issues.apache.org/jira/browse/WW-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukasz Lenart updated WW-4848:
------------------------------
Description:
The {{s:if}} tag has the side effect of assigning to an existing object
if the comparison is badly formed using {{=}} instead of {{==}}
{code:html}
<s:if test="user.id = 0">
//at this point the user.id is now 0 not its original value
</s:if>
{code}
even though this is clearly badly formed, the test should not assign anything
to the object
was:
The <s:if tag has the side effect of assigning to an existing object
if the comparison is badly formed using = instead of ==
<s:if test="user.id = 0">
//at this point the user.id is now 0 not its original value
</s:if>
even though this is clearly badly formed, the test should not assign anything
to the object
> The if test can accidently incorrectly assign a new value to an object
> ----------------------------------------------------------------------
>
> Key: WW-4848
> URL: https://issues.apache.org/jira/browse/WW-4848
> Project: Struts 2
> Issue Type: Bug
> Reporter: Alan Comeau
> Priority: Minor
> Fix For: 2.5.x
>
>
> The {{s:if}} tag has the side effect of assigning to an existing object
> if the comparison is badly formed using {{=}} instead of {{==}}
> {code:html}
> <s:if test="user.id = 0">
> //at this point the user.id is now 0 not its original value
> </s:if>
> {code}
> even though this is clearly badly formed, the test should not assign anything
> to the object
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
