Chris,
Thanks for your insightful wiki on this subject. This seems a
much lighter weight solution to the Acegi Authentication. ( the latter
requires many more jar file downloads related to Spring) I do have a
question that's been on my mind for some time now. Is it standard
practice in Tapestry for page redirects to throw exceptions? Is there
another method that preserves the current state after a redirection?
Say for instance, a user bookmarks a page and returns to it two
days later. How does one determine the resultant page after a
successful login? Using the current code, the user's session would be
invalid and forced to the login page when trying to access the bookmark
via an exception. How would you save the destination url for the user
after he/she logs in successfully? Rather is there a "standard" way
that Tapestry does this? Would you have to put it into the ASM and then
access the ASM during login to determine the users destination? Is
there another mechanism?
Thanks,
Michael
-----Original Message-----
From: Chris Lewis [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 07, 2007 8:10 AM
To: Tapestry users
Subject: Re: T5 how to control login state
I've created a new article to supplement the first, showing how to
access thread-specific ASOs from a singleton service. It's on the wiki:
http://wiki.apache.org/tapestry/Tapestry5HowToCreateADispatcher2
sincerely,
chris
Angelo Chen wrote:
> Hi Chris,
>
> I'm interested in your approach and read already the wiki, you spent a
> lot to explain the concept behind, can you also provide a
> simple/complete sample code for that? thanks.
>
> A.C.
>
>
> Chris Lewis-5 wrote:
>
>> I'll update the wiki.
>>
>> chris
>>
>>
>> lyifan wrote:
>>
>>> Thanks a lot everyone. Finally the BasePase way works
>>>
>>> But the d
>>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
