[jira] [Closed] (TAP5-58) Tapestry should be smarter about event handler methods refiring events with the same name

["Massimo Lusetti (JIRA)" <ji...@apache.org>]

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

Massimo Lusetti closed TAP5-58.
-------------------------------

       Resolution: Won't Fix
    Fix Version/s: 5.3

Please open a new one for 5.3 if this still applicable

> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
>                 Key: TAP5-58
>                 URL: https://issues.apache.org/jira/browse/TAP5-58
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered.  Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.

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