ListenerInvokerFilter provides no way to find out what listener method is being
invoked
---------------------------------------------------------------------------------------
Key: TAPESTRY-838
URL: http://issues.apache.org/jira/browse/TAPESTRY-838
Project: Tapestry
Type: Wish
Components: Framework
Versions: 4.0
Reporter: Chris Conrad
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
