You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2008/03/09 22:37:46 UTC

[jira] Updated: (TAPESTRY-2182) NullPointerExceptions, due to reading nested properties that do not suppress null values, do not indicate problematic expression for AbstractPropertyOutput derivatives

     [ https://issues.apache.org/jira/browse/TAPESTRY-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAPESTRY-2182:
-------------------------------------------

    Summary: NullPointerExceptions, due to reading nested properties that do not suppress null values, do not indicate problematic expression for AbstractPropertyOutput derivatives  (was: NullPointerExceptions, due to reading nested properties that do not suppress null values, do not indicate problematic expression for AbstractPropertyOutput derivatives.)

> 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.11
>
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org