To comment a little further, from my reading of the Tapestry Hivedoc there are two places I can hook into to intercept calls to components/pages: tapestry.listener.ListenerInvoker and tapestry.request.ServletRequestServicerPipeline/tapestry.request.WebRequestServicerPipeline. The latter is more or less out of the question, you can perform interceptions at an application granularity, you have no access to the current page or components until after everything is rendered. The first is almost there but it provides only page level granularity. You can figure out the current page and you can figure out what component triggered the listener method invocation, but there is no way to see what method was actually invoked and on what object it was invoked on.
My motivation for this is I'd like to implement some of the features of JBoss Seam into my application. This possible if I stay completely within the realm of Hivemind components, but that requires me to put a lot of effort into creating components and whatnot for simple data collection pages. By providing a more granular interception model for listener method calls I can avoid creating extraneous services which are only necessary for their abillity to be intercepted.