The injected sessionMap is sufficient if all you need to do is get, set and remove session attributes. For other things like invalidating the session, you should implement ServletRequestAware and retrieve the session using the injected HttpServletRequest.
As you can see from the source code, the sessionMap doesn't give you access to the request. The serialVersionUID has nothing to do with the session ID, it's for standard Java serialization[1]. Cheers, GB [1] http://java.sun.com/j2se/1.5.0/docs/api/java/io/Serializable.html http://java.sun.com/j2se/1.5.0/docs/api/java/io/Serializable.html Thank you very much. I found the source code and looked at it and now I understand perfectly. I can't believe I missed all that info the SessionMap object. So then once you have a sessionMap I assume that that the sessionMap is the only thing you need for accessing the request, clearing the session, and invalidating the session, right? Also, is the serialVersionUID in fact the same thing as the sessionId? Guillaume Bilodeau wrote: > > I suggest you have a look at the source code for the > org.apache.struts2.dispatcher.SessionMap, this is what gets injected to > your SessionAware action. As you'll see it's simply a class that > implements the java.util.Map interface and wraps a HttpSession. Calls to > the get, put and remove methods all impact the underlying session object. > It's not a separate HashMap. > > Cheers, > GB > > -- View this message in context: http://www.nabble.com/Does-Struts-2-support-clustering--tp16609897p16628206.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
