Tapestry
  1. Tapestry
  2. TAPESTRY-2097

Render exceptions should identify the components that are actively rendering

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.9
    • Fix Version/s: 5.0.10
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      This can be very handy when figuring out how and where things have gone wrong. Because of how Tapestry's render queue works, it is hard to extract this information from a stack trace or from the debugger.

        Activity

        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12568369 ] jira [ 12591428 ]
        Mark Thomas made changes -
        Workflow jira [ 12422234 ] Default workflow, editable Closed status [ 12568369 ]
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Status Open [ 1 ] Closed [ 6 ]
        Fix Version/s 5.0.10 [ 12312936 ]
        Resolution Fixed [ 1 ]
        Howard M. Lewis Ship created issue -

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development