Thiago,
I know that on pages or components navigation is controlled by the return
type. ( page class, String, etc) My question has to do with how to deal with
navigation before any page or component renders. In other frameworks you can
have a workflows specified outside the application in XML, a database, etc.
These workflows determine page flow. In tapestry, however this is not the case
that I've seen.
I've partially implemented what Chris just posted about the Dispatcher
but using the RequestFilter like Massimo suggested. What I don't know how to
do is to cleanly specify where to go after logging the user in without having
to manually stuff something into the HttpSession about where to return in the
page flow.
Any ideas?
--Michael
-----Original Message-----
From: Thiago H de Paula Figueiredo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 07, 2007 10:52 AM
To: Tapestry users
Subject: Re: T5 how to control login state
On Wed, 07 Nov 2007 16:40:45 -0200, Nguyen, Michael <[EMAIL PROTECTED]> wrote:
> Chris,
> Is it standard
> practice in Tapestry for page redirects to throw exceptions?
That's true for Tapestry 4.x, but not for Tapestry 5.
--
Thiago H. de Paula Figueiredo
Desenvolvedor, Instrutor e Consultor de Tecnologia Eteg Tecnologia da
Informação Ltda.
http://www.eteg.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
