Putting in /common/lib ensures the classes are loaded by the system classloader. The application classes are loaded by the 'war classloader' which is a child of system classloader. You can access the classes loaded by the system classloader from the web applications.
-----Original Message----- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 21, 2004 4:39 PM To: Tomcat Users List Subject: RE: Single session across webapps There is no actual way that I know of to directly share sessions. I'd imagine what the person meant was if you create a singleton in /common/lib, then you need to store all the session information for each user in that singleton, then when you enter a new app you should check in the singleton to see if the information for that user has been stored and if so then replicate all the information there into the current session. Not exactly session sharing but a shared location for objects common across webapps. Ta Matt -----Original Message----- From: Todd O'Bryan [mailto:[EMAIL PROTECTED] Sent: 21 January 2004 11:04 To: Tomcat Users List Subject: Single session across webapps I asked a much more involved question before and no one responded, so... Is there a way to share sessions across webapps running in the same container? A previous message talked about putting a singleton in /common/lib, but wasn't too specific about how to work it. Could somebody be more specific or direct me somewhere that is? Thanks, Todd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
