Hello, It's not really clear what you mean and maybe you need to tell us what you want to do.
A Wicket session stores it's attributes into an implementation of the ISessionStore interface, but the default the store is HttpSessionStore, so the HttpSession. On the other hand, the wicket session can exist in a temporary state for the duration of the request and not have a HttpSession created. See bind(...) method in HttpSessionStore and you can see the Wicket session object being stored in a httpsession attribute when the Wicket session needs to be persistent. setAttribute(request, Session.SESSION_ATTRIBUTE_NAME, newSession); -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Set-Wicket-User-Session-to-Servlet-s-HttpSession-tp4355593p4355644.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
