Tapestry
  1. Tapestry
  2. TAPESTRY-2401

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

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical 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

        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Resolution Fixed [ 1 ]
        Fix Version/s 5.0.12 [ 12313048 ]
        Status Open [ 1 ] Closed [ 6 ]
        Mark Thomas made changes -
        Workflow jira [ 12430150 ] Default workflow, editable Closed status [ 12568695 ]
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568695 ] jira [ 12591722 ]

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development