You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/07/08 02:24:16 UTC
[jira] [Assigned] (TAP5-1227) Binding a parameter whose type is
primitive to null results in a difficult to understand NullPointerException
[ https://issues.apache.org/jira/browse/TAP5-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1227:
------------------------------------------
Assignee: Howard M. Lewis Ship
> Binding a parameter whose type is primitive to null results in a difficult to understand NullPointerException
> -------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1227
> URL: https://issues.apache.org/jira/browse/TAP5-1227
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> NPE is appropriate, but a blank message is not. The message should be something like:
> "Parameter com.example.components.Layout.section is primitive type int and may not be bound to null. You should convert this parameter to type java.lang.Integer."
> Possibly we could get some similar effect by automatically forcing allowNull to false for primitive type parameters.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira