Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-838

ListenerInvokerFilter provides no way to find out what listener method is being invoked

    Details

    • Type: Wish
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 4.1.2
    • Component/s: Framework
    • Labels:
      None

      Description

      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?

        Attachments

          Activity

            People

            • Assignee:
              jkuhnert Jesse Kuhnert
              Reporter:
              rhavyn Chris Conrad
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: