Re: Is onActivate a robust place for authentication?
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]
Re: Is onActivate a robust place for authentication?
Sorry, everybody, I should have mentioned that I'm in T5. Looking for a solution. Bill On 5/18/07, Martino Piccinato <[EMAIL PROTECTED]> wrote: I think what you are looking for is interface PageValidateListener http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/event/PageValidateListener.html it's thought just for this kind of things afaik. On 5/18/07, Eric Chatellier <[EMAIL PROTECTED]> wrote: > > 2007/5/18, Bill Holloway <[EMAIL PROTECTED]>: > > 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 > > I bill > > I'm interested by the answer too... > > Where can we put redirect to login form (for exmple) if the user has > not logged in ? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "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]
Re: Is onActivate a robust place for authentication?
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
Re: Is onActivate a robust place for authentication?
This doesn't exist in tapestry 5 2007/5/18, Martino Piccinato <[EMAIL PROTECTED]>: I think what you are looking for is interface PageValidateListener http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/event/PageValidateListener.html it's thought just for this kind of things afaik. On 5/18/07, Eric Chatellier <[EMAIL PROTECTED]> wrote: > > 2007/5/18, Bill Holloway <[EMAIL PROTECTED]>: > > 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 > > I bill > > I'm interested by the answer too... > > Where can we put redirect to login form (for exmple) if the user has > not logged in ? > > - > 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]
Re: Is onActivate a robust place for authentication?
I think what you are looking for is interface PageValidateListener http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/event/PageValidateListener.html it's thought just for this kind of things afaik. On 5/18/07, Eric Chatellier <[EMAIL PROTECTED]> wrote: 2007/5/18, Bill Holloway <[EMAIL PROTECTED]>: > 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 I bill I'm interested by the answer too... Where can we put redirect to login form (for exmple) if the user has not logged in ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is onActivate a robust place for authentication?
2007/5/18, Bill Holloway <[EMAIL PROTECTED]>: 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 I bill I'm interested by the answer too... Where can we put redirect to login form (for exmple) if the user has not logged in ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
