[
https://issues.apache.org/jira/browse/TAPESTRY-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570843#action_12570843
]
Kevin Menard commented on TAPESTRY-2182:
----------------------------------------
Digging in a bit more, this only applies to nested properties. Incidentally,
it applies to more than just Grid as well. It applies to anything that extends
AbstractPropertyOutput. I'll have to check it even makes sense to handle this
in a larger sense with the conduit wrapper.
Note that the NPE isn't the issue of contention. The docs indicate that "?."
should be used to suppress null values. The problem is that the current
exception doesn't really give any helpful information as to the cause of the
NPE.
> Indicate null property's name if NPE encountered in a Grid.
> -----------------------------------------------------------
>
> 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
> 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]
