I see. I didn't read that very nice comment!! Thanks for pointing it out! I can see I should extend EnterpriseCacheSessionDAO and add an overridden method.
BTW, I did try to extend SimpleSession, but this seemed difficult because of all the private fields in it -- but that is indeed an alternative way to go. In any case, what I am trying to do is to control which session attributes to write and which to skip. Our session object contains very large JSF objects (don't ask me why!) which contains its state, some 300k in size. I would like to skip writing out these objects. Then the session clustering system can be more lean. Thanks for your quick response, Dan -- View this message in context: http://shiro-user.582556.n2.nabble.com/Replacing-SimpleSession-tp6821608p6821714.html Sent from the Shiro User mailing list archive at Nabble.com.
