On Thursday 26 April 2007 1:02 pm, Eelco Hillenius escreveu:
> > I need to work with a servlet from another group and they need to see the
> > user as an attribute on the HttpSession. It seems as though
> > setAttribute on my wicket.Session doesn't actually set it on the
> > HttpSession. Is that correct?
>
> Typicaly it does, but it depends on your configuration. Session
> delegates this to the ISessionStore your application uses. For Wicket
> 1.3, the default store is SecondLevelCacheSessionStore, which extends
> HttpSessionStore (which was the default for 1.2). Both these session
> stores pass and the attributes from/ to the underlying HttpSession.
So I found that it indeed stores my user as an attribute on the http
session,
but it stores it with the following prefix: "wicket:/app/login:", so the
servlet that's looking up "user" doesn't find it. So I guess that going
directly to the HttpSession to store the user is the only thing I can do.
Thanks,
Tom
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
