On 19/01/18 20:40, Christopher Schultz wrote: > Mark, > > On 1/19/18 3:04 AM, Mark Thomas wrote: >> On 18/01/18 20:11, Christopher Schultz wrote: >>> Speaking of "expensive" objects, we do have a "user" object in >>> the session. If the user isn't there, we throw all kinds of >>> exceptions and don't let "users" actually do anything except go >>> to their login pages. >>> >>> So I expect that I can (a) always rely on a "user" attribute >>> being in the session and (b) I can use that as my monitor. > >> I'd check how it is wrapped before you do that. From memory, I'm >> not sure the same wrapper will always be used. > > That "user" attribute is application-defined. I don't believe Tomcat > wraps any application objects that are stored in the session, does it? > Or did I misunderstand your statement?
No. I mis-understood your use of 'we'. I thought you meant Tomcat. Tomcat won't wrap an application defined objects. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
