You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/07/03 23:44:49 UTC

[jira] Assigned: (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 reassigned TAP5-1199:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.