Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-2401

NullPointerExceptions inside component bindings need to do a better job of explaining what was null

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.0.11
    • Fix Version/s: 5.0.12
    • Component/s: None
    • Labels:
      None

      Description

      Getting an NPE inside a dynamically generated class is not helpful. Tapestry should check for null after each method in the chain of property names is executed.

        Activity

        There are no comments yet on this issue.

          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:

              Development