It's okay to use it in situations like this. We just don't want to make it too easy for people to use for the wrong reasons. You might want to take a look at wicket.protocol.http.servlet.WicketSessionFilter too. That filter exposes the wicket session object, so that you can use it in a strongly typed way outside of Wicket applications.
Eelco On 3/1/06, John Patterson <[EMAIL PROTECTED]> wrote: > On Wednesday 01 Mar 2006 13:51, Juergen Donnerstag wrote: > > What do you need it for? > > > > I am migrating my web application from WebWork to Wicket. All new > functionality is written in Wicket but I need to share some objects with the > old code such as the currently logged in user. This is stored in the http > session. Using the HttpSessionStore attributes that I set are prefixed. > > I guess I could have changed my old code to use the wicket prefix. > > John. > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
