[
https://issues.apache.org/jira/browse/WW-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080381#comment-13080381
]
Andreas Krüger commented on WW-3318:
-------------------------------------
Hello, Lukasz,
no news.
Maybe with the exception that I no longer use struts.
If you have satiesfied yourself that throwExceptionOnFailure leads to throwing
an exception on ANY attempt to call nonexisting code, feel free to close this.
"ANY" attempt includes debug mode, production mode, and all other settings you
can think of.
On the other hand, maybe you think that there are scenarios where failure to
execute code (e.g., because that code does not even exist) should NOT throw an
exception, irregardless of the fact that the user has specifically requested
throwExceptionOnFailure.
If you think that way, we disagree.
I'd be happy to continue to discuss such scenarios. For starters, I'd be
curious what you think about my "fire alam" example given above.
Regards, Andreas
> throwExceptionOnFailure=true doesn't detect undefined property burried in OGNL
> ------------------------------------------------------------------------------
>
> Key: WW-3318
> URL: https://issues.apache.org/jira/browse/WW-3318
> Project: Struts 2
> Issue Type: Bug
> Components: Value Stack
> Affects Versions: 2.1.8
> Reporter: Andreas Krüger
> Assignee: Lukasz Lenart
> Fix For: 2.2.x
>
>
> Setup:
> struts.el.throwExceptionOnFailure=true in struts.properties
> In the value stack, there is no object which has any property "xxx"
> The JSP has <s:property value="xxx == null ? 'Not yet determined' : xxx" />
> Expected behaviour: As the property xxx is not defined, this should throw an
> exception.
> Behaviour seen: The string "Not yet determined" gets inserted into the HTML
> output as if nothing were wrong.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
