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 mojoRising wrote: > > Thank you all for your help. I think we have it resolved and it was indeed > the WLCookieName parameter (JSESSIONID) in the weblogic plugin that was > set incorrectly. This has led to heavy discussion however with regards to > this question: > Is it really a good idea to implement the SessionAware interface and use a > separate Hashmap to hold the user's session data? Would it not be perhaps > safer and more efficient (and reduce the possibility of clustered session > replication issues) to simply get the session yourself and set the > attributes directly into it? What benefit is there to making struts the > middleman and using a separate Hashmap? We are having this debate > currently at my co. and I am lacking a convincing reason to avoid dealing > directly with the session. THanks! > > > -- View this message in context: http://www.nabble.com/Does-Struts-2-support-clustering--tp16609897p16628146.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]
