Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1227

Binding a parameter whose type is primitive to null results in a difficult to understand NullPointerException

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              hlship Howard M. Lewis Ship
              Reporter:
              hlship Howard M. Lewis Ship
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: