On Tue, 01 Mar 2011 13:03:34 -0300, Rich M <rich...@moremagic.com> wrote:
Hi,
Hi!
I currently have a Dispatcher implementation to handle page and asset
requests in order to process authentication and security logic as
necessary. However, it appears to me that (at least in 5.1) the
Dispatcher does not intercept any ActionLinks, EventLinks, form events,
or otherwise related client-side triggers that are not page requests.
These scenarios should be handled by implementing one of the Tapestry
filter pipelines.
Dispatchers are supposed to return content after handling a request.
Is there a service or service interface to implement that would provide
an opportunity to step in and intercept these requests before a
page/component catches them?
Implement a ComponentRequestFilter and contribute it to the
ComponentRequestHandler service.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
