[
https://issues.apache.org/jira/browse/WW-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160324#comment-13160324
]
Andreas Krüger commented on WW-3318:
------------------------------------
> You want the same behaviour of the throwExceptionOnFailure in devMode and in
> production ?
Yes.
Just because this is production, I do not want Struts to ignore a conscious
configuration choice I have made.
> To see what goes wrong with your application in production ?
To see WHEN / WHETHER something goes wrong in production.
For production, I think it is especially important that results are reliable.
I do not want to be shown a wrong result in production, if those could be
caught.
I again point out my fireAlam example from 13/Apr/10. The (fictious) story goes
like this:
Someone mistyped (the "r" is missing in "Alam"). Test did not catch the bug.
The bug reaches production.
Then, there IS a fire alarm. With exceptions ignored, the application wrongly
informs people "no alarm". People that trust the application will make WRONG
decisions. In a fire alarm situation, this can be dangerous. In other
situations (we had a banking application back when I raised the bug), this
could just be very, very expensive.
If my application is broken and has a bug, I want it to communicate "I am
broken, I have a bug". This is much less dangerous. This way, the application
will not inform people incorrectly.
There is much less danger in dev environment. Developers will not do anything
dangerous or expensive if the application informs them incorrectly. The danger
from surpressed exceptions is in production.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
