[jira] [Updated] (TAP5-146) Provide some way to get the component that fired an event

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-146:
--------------------------------

    Labels: bulk-close-candidate  (was: tapestry5-review-for-closing)

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> Provide some way to get the component that fired an event
> ---------------------------------------------------------
>
>                 Key: TAP5-146
>                 URL: https://issues.apache.org/jira/browse/TAP5-146
>             Project: Tapestry 5
>          Issue Type: New Feature
>    Affects Versions: 5.0.15
>            Reporter: Thiago H. de Paula Figueiredo
>              Labels: bulk-close-candidate
>
> It would be very nice to have event handler methods know what component fired that event, specially for mixins.
> There's a discussion in the mailing list: http://www.nabble.com/forum/ViewPost.jtp?post=18157269&framed=y.
> Howard said:
> We could change Event to expose the source
> Component ... we could also change the EventWorker logic to see if the
> sole parameter to an event handler method is of type ComponentEvent
> and pass the event directly to the event handler method.



--
This message was sent by Atlassian JIRA
(v6.2#6252)