Tapestry 5
  1. Tapestry 5
  2. TAP5-1199

ClassTransformation should include an API specifically for adding a component event handler to a component class

    Details

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

      Description

      There's a bunch of steps in making this happen; it would be nice if it was just something like:

      transformation.addEventHandler("activate", 0, new ComponentEventHandler(Event event)

      { ... }

      );

      The number is the minimum number of parameters.

      The semantics of this is that the handler is invoked first, with an invocation.proceed() at the end. The handler is not invoked if the event is aborted. The result of the invocation is overridden to true if the handler is invoked.

        Activity

        Hide
        Hudson added a comment -

        Integrated in tapestry-5.2-freestyle #153 (See http://hudson.zones.apache.org/hudson/job/tapestry-5.2-freestyle/153/)

        Show
        Hudson added a comment - Integrated in tapestry-5.2-freestyle #153 (See http://hudson.zones.apache.org/hudson/job/tapestry-5.2-freestyle/153/ )
        Hide
        Howard M. Lewis Ship added a comment -

        Previously fixed; it is present in the TransformationSupport passed to ComponentClassTransformWorker2.

        Show
        Howard M. Lewis Ship added a comment - Previously fixed; it is present in the TransformationSupport passed to ComponentClassTransformWorker2.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development