On Tue, 01 Mar 2011 14:55:52 -0300, Rich M <rich...@moremagic.com> wrote:
Oh, I see. Perhaps then it's reasonable to say I was mislead by this
Tapestry wiki page
http://wiki.apache.org/tapestry/Tapestry5HowToCreateADispatcher ? This
is pretty much exactly what I adapted to my application half a year ago,
'AccessController' name and all.
That's a wiki page, not part of the official documentation.
I am in fact using the Dispatcher to redirect to a login page with an
expired context, I suppose I'm not entirely clear yet between the Wiki
and my working implementation why Dispatcher isn't appropriate.
In this case, thinking it over, it's not inappropriate, just not as
appropriate as a filter.
Perhaps its a case of, 'it will work, but that's not what it was meant
for'? Or are there some nuances to the ComponentRequestHandler pipeline
that make it a more robust authentication point?
It's only invoked for page render and event requests, not for asset ones.
--
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
