[
https://issues.apache.org/jira/browse/TAPESTRY-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570865#action_12570865
]
Kevin Menard commented on TAPESTRY-2182:
----------------------------------------
I looked at addressing this property conduit level, but that's way too
invasive. The core issue is that the user is at least one level away from the
NPE because Grid et al. hide the implementation. For custom components, it
really shouldn't be much of an issue because the highlighted template will show
the user's problematic code.
> NullPointerExceptions due to reading nested properties that do not suppress
> null values do not indicate problematic expression for AbstractPropertyOutput
> derivatives.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-2182
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2182
> Project: Tapestry
> Issue Type: Improvement
> Components: Core Components
> Affects Versions: 5.0.10
> Reporter: Kevin Menard
> Assignee: Kevin Menard
> Priority: Minor
> Fix For: 5.0 Next Release
>
>
> When supplying a data source to a grid, if any instance in that data source
> has a null value for any of the rendered properties, an NPE will be thrown.
> Unfortunately, the error message does not indicate what the problematic
> property is, so the developer has to use a hold-one-out strategy to debug the
> problem. Indicating the column with the problem would help considerably. If
> there were a way to meaningfully identify the row as well, that would be
> extra nice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
