Yeah, that's how I'm doing this now. Having a Tapestry annotation
like @Secure that invokes your pipeline contribution sounds the most
solid.
Bill
On 5/18/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
For the meantime, an "activate" event handler method (in a base class) is
how I've envisioned authentication.
However, I want to open up a kind of pipeline between the Dispatcher and the
PageLinkHandler that can be injected, so that you can do this kind of
operation across the entire application.
On 5/17/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
>
> I'm not sure yet how to integrate ACEGI, but I can look at an ASO in
> onActivate for a page. Is returning a page name from onActivate() a
> robust solution for basic user authentication?
>
> Bill
>
> --
> "The future is here. It's just not evenly distributed yet."
>
> -- Traditional
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
--
"The future is here. It's just not evenly distributed yet."
-- Traditional
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
