[ 
https://issues.apache.org/jira/browse/WW-4999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854259#comment-16854259
 ] 

ASF subversion and git services commented on WW-4999:
-----------------------------------------------------

Commit 0999fba8c496588bb55df0a025875cc76b35ce96 in struts's branch 
refs/heads/struts-2-5-x from Yasser Zamani
[ https://gitbox.apache.org/repos/asf?p=struts.git;h=0999fba ]

not log user exceptions as missing properties (WW-4999)

Also reaks loop on user method exceptions - but continue to next objects in 
stack on NoSuchMethodException.


> Can't get OgnlValueStack log even if enable logMissingProperties
> ----------------------------------------------------------------
>
>                 Key: WW-4999
>                 URL: https://issues.apache.org/jira/browse/WW-4999
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Value Stack
>    Affects Versions: 2.5.17
>            Reporter: Quincy Qu
>            Assignee: Yasser Zamani
>            Priority: Major
>             Fix For: 2.5.21, 2.6
>
>
> I'm in devMode, enabled logMissingProperties and expect to see missing 
> property warning in the log. I was surprised that I can't get the missing 
> property log even if logMissingProperties is set true. The application run 
> smoothly and skip the missing property - as expected though.
> In another run, I enabled both logMissingProperties and 
> throwExceptionOnFailure. This time the application crash at the missing 
> property and I can get both logs and exception.
> After I dive deeper using debugger, I convince myself the config is good, 
> since devMode and logMissingProperties are true at runtime in OgnlValueStack.
> I was confused, why we can't get missing property log without throwing 
> OgnlException? 
> Are we able to enter handleOgnlException(String expr, boolean 
> throwExceptionOnFailure, OgnlException e)  at all if throwExceptionOnFailure 
> is false, in which my expected log is written?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to