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 2010/08/03 00:32:19 UTC
[jira] Created: (TAP5-1227) Binding a parameter whose type is
primitive to null results in a difficult to understand NullPointerException
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
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.
-
You can reply to this email to add a comment to the issue online.