RE: [s2] Question about SessionAware docs.

From: Tom Schneider [mailto:[EMAIL PROTECTED] > Actually your explanation is not quite 100% correct. The interceptor > injects a Map that is backed by the HttpSession. So puts and gets to > the Map will actually be puts and gets to the HttpSession. (Very > clever IMO) Ah, okay. That's handy an

Re: [s2] Question about SessionAware docs.

Actually your explanation is not quite 100% correct. The interceptor injects a Map that is backed by the HttpSession. So puts and gets to the Map will actually be puts and gets to the HttpSession. (Very clever IMO) You have a valid point about the javadoc. My guess is that at one point it act

[s2] Question about SessionAware docs.

The JavaDoc for SessionAware states: "Note that using this interface makes the Action tied to a servlet environment, so it should be avoided if possible since things like unit testing will become more difficult." I'm not entirely sure that's accurate, as it isn't *explicitly* tied to the servlet