Michael,
I'm pretty sure tapestry has no such mechanism. The short answer to your
question is that you'd have to store these things (page names of
failed/unauthorized access attempts) as an ASO, and then pull it out
after logging in. I've not worked with a system like you're talking
about, but am glad that T5 is lacking in XML. However something like
this could probably useful, and may be doable in the form of some service.
First of all I should point out the link to how you can implement a
redirect exception:
http://wiki.apache.org/tapestry/Tapestry5RedirectException
This is a bit of a hack, but demonstrates how you can get the exception
back, as well as use decoration.
I think what you want is attainable through services, and probably as a
dispatcher. I'll need someone with a more thorough understanding of T5
to chime in on this, especially someone that has used what you are
looking for. If a dispatcher handles the request, it is responsible for
sending the response (HTTP and content) to the client. With that you
should have the basics for what you want. You may also have this option
with RequestFilters, but I'm not sure.
Anyway, someone with more knowledge on the workings would be good to
hear. I'd like to know how you fare as I'm always in the market for a
better way to do things.
Sincerely,
chris
Nguyen, Michael wrote:
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]
