Take a look at wicket-auth-roles. This provides the usual security stuff, and you can easily also check for a set cookie. Just implement your own authorisation scheme. Martijn
On 2/12/08, Roland Huss <[EMAIL PROTECTED]> wrote: > > > Hi, > > what is the best place to hook into the request cycle > before a page gets processed ? I looked through > http://cwiki.apache.org/WICKET/lifecycle-of-a-wicket-application.html but > the > information there seems to be a bit outdated ("the Session returned by the > Application > is asked to create a RequestCycle object using the Session's request > cycle > factory", > but there's nothing like a request cycle factory which can be obtained > from > a Session in 1.3) > > Is there a more accurate documentation of a request's lifecycle somewhere > else ? > > My use case is as follows: Before any page is processed I want to look up > in > the Session, > whether a user is authenticated. If not, it is checked wheter a certain > hash > stored in a Cookie > (if any) is stored in the DB and the associated user then is put into the > session, providing some sort > of 'keep me logged in' functionality. (The 'remember me' feature of the > SignInPanel is not enough for > me, since I want a transparent login without moving over the login page). > Of > course, if there is already > support for this kind of feature out of the box somewhere, I would be > happy > for getting a pointer, too. > > thanx ... > > ... roland > -- > View this message in context: > http://www.nabble.com/Hook-into-RequestCycle---tp15428634p15428634.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.1 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.1
