You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/09/23 22:11:26 UTC

[jira] [Closed] (TAP5-1199) ClassTransformation should include an API specifically for adding a component event handler to a component class

     [ https://issues.apache.org/jira/browse/TAP5-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1199.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3
         Assignee: Howard M. Lewis Ship

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

> ClassTransformation should include an API specifically for adding a component event handler to a component class
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1199
>                 URL: https://issues.apache.org/jira/browse/TAP5-1199
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3
>
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira