[
https://issues.apache.org/jira/browse/TAP5-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069406#comment-13069406
]
Mihail Slobodyanuk commented on TAP5-146:
-----------------------------------------
My proposition for API is use annotated parameter in event handler by this
syntax:
void onSomeEvent(@Component Component component, String firstContextParam,
String secondContextParam){
...
}
> 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
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
