[jira] [Commented] (TAP5-1672) PropertyDisplay component will swallow NPEs when evaluating the property, leaving no clue about the actual NPE

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on TAP5-1672:
-------------------------------------------------------

Commit 639c57df2363181a8eb78d1a1653b7b73e9e614a in tapestry-5's branch refs/heads/master from [~hlship]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=639c57d ]

TAP5-1672: Provide more info when PropertyDisplay component hits an NPE


> PropertyDisplay component will swallow NPEs when evaluating the property, leaving no clue about the actual NPE
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1672
>                 URL: https://issues.apache.org/jira/browse/TAP5-1672
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2
>            Reporter: Wulf Wechsung
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: NPE, propertydisplay
>             Fix For: 5.4
>
>
> Situation:
> A property (prop) on an object is realized by a getter (ie getProp()). The getter throws a NullPointerException on invokation. 
> Observed Behavior:
> Trying to display the property, the propertydisplay component reports an error "Property 'currentlyOverdue' contains a null value in the path." without any trace of the underlying NPE.
> Expected Behavior:
> The error report should include the stack-trace off the NPE and the error message could also be a bit clearer.
> It's possible that propertydisplay also fails to report other exceptions that occur in a getter.



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