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

A user defined activate event handler appears to execute *before* the event handler supplied by @PageActivationContext, making defensive coding impossible

    Details

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

      Description

      A common technique is to provide a no-argumentes activate event handler method that can check to see if the PAC is null, and return a page (or other redirect causing result). However, since the @PageActivationContext-related event handler executes too late, the field will always be null when that method executes.

      Workaround: Don't use @PageActivationContext

        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: