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

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.2
• Fix Version/s: 5.4
• Component/s: tapestry-core
• Labels: NPE propertydisplay
• Assignee: Howard Lewis Ship
• Reporter: Wulf Wechsung
• Created: 27/Sep/11 11:35
• Updated: 17/Apr/14 23:20
• Resolved: 17/Apr/14 23:20

Description

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.