I'm looking to add a chain-of-command around handling of render and action
requests; you'll be able to plug in there.

On 9/24/07, Ben Tomasini <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am working on an application that requires a logged in user for access
> to
> any of the pages.  My plan is to create a login form and store the logged
> in
> user in an ASO.  I understand that I can implement an onActivate() on each
> of my pages, check to see if the user exists in the ASO, and if not,
> redirect the user to the login page.  I could put this method into an
> abstract page which all of my pages extend from; however, I would rather
> not
> put that kind of constraint and burden on page development.
>
> Is there a more global way to enforce that an ASO exists, and if not,
> redirect to a page?
>
> Ben
>



-- 
Howard M. Lewis Ship
Partner and Senior Architect at Feature50

Creator Apache Tapestry and Apache HiveMind

Reply via email to