[jira] Resolved: (TAPESTRY-838) ListenerInvokerFilter provides no way to find out what listener method is being invoked

["Jesse Kuhnert (JIRA)" <de...@tapestry.apache.org>]

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

Jesse Kuhnert resolved TAPESTRY-838.
------------------------------------

    Resolution: Fixed
      Assignee: Jesse Kuhnert

Added getMethodName() to IActionListener and ListenerMethodInvoker. 

> ListenerInvokerFilter provides no way to find out what listener method is being invoked
> ---------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-838
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-838
>             Project: Tapestry
>          Issue Type: Wish
>          Components: Framework
>    Affects Versions: 4.0
>            Reporter: Chris Conrad
>         Assigned To: Jesse Kuhnert
>             Fix For: 4.1.2
>
>
> The ListenerInvokerFilter pipeline appears to be the only place where you can intercept listener method calls.  Obviously this can be useful for a variety of features, the Javadoc even suggests it's a good place to put transaction handling.  However, there does not seem to be any way to find out what listener method is being invoked.  Without that information the only metadata you can provide to the ListenerInvokerFilter is class level metadata since you can get access to the current page through the IRequestCycle.  Would it be possible to expose either the listener method being invoked, or in the alternative, provide some form of interception support to pages?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org