Tomcat 3.3.x provides the lib/apps directory (see the README file in there) for Jar files that contains classes to be shared among all webapps.
Sessions are not cross-context. Sessions are specific to the webapp they are created in for security reasons. Sessions are created via a "request.getSession()" call in your servlet or JSP. So, you can use the same class definition of a bean in two separate webapps if the class definition is in $TOMCAT_HOME/lib/apps... (or alternatively, in the WEB-INF/lib directories of your two webapps, but that is just wasted space). The webapps will create two separate instances of your bean. Regards, Michael ----- Original Message ----- From: "Power-Netz (Schwarz)" <[EMAIL PROTECTED]> To: "tomcat liste" <[EMAIL PROTECTED]> Sent: Monday, July 29, 2002 5:58 AM Subject: TC and applicationwide beans > > Hi, > > can tomcat swap beans from one application to another if both use the > classes? > > If I have a webapp A which granted access to the system and uses a login > bean to store > the data, does tc accept this bean ( in the same session ) on the webapp B > with same classes? > Or is a new session created if the user switches from one app to another??? > > (related to tc 3.3.2dev) > > Ihr Support-Team > > >>> POWER-NETZ� > Full-Service-Provider <<< > > Online-Support: > Support: 0190 - 15 11 15 (EUR 0,62/Min) > http://Support.Power-Netz.de (kostenlos) > http://Support.Power-Netz.com (kostenlos) > > Vertrieb Tel: 01805 - 57 35 57 (EUR 0,12/Min.) > Vertrieb Fax: 01805 - 57 45 57 (EUR 0,12/Min.) > > Power-Netz > Am Plan 1 > 37581 Bad Gandersheim > > http://www.Power-Netz.de > mailto:[EMAIL PROTECTED] > > > +=========================================+ > <----------I N F O C E N T E R----------> > + Senden Sie eine leere e-mail an: > + Providerwechsel: mailto:[EMAIL PROTECTED] > + Daten/Preise Webspace: mailto:[EMAIL PROTECTED] > + Reseller-Programm: mailto:[EMAIL PROTECTED] > + Dedizierte Server: mailto:[EMAIL PROTECTED] > + Adult/Erotikserver: mailto:[EMAIL PROTECTED] > + Domainpreise: mailto:[EMAIL PROTECTED] > + Domain-Nameserver: mailto:[EMAIL PROTECTED] > + SSL-Zertifikate: mailto:[EMAIL PROTECTED] > + Geschaeftsbedingungen: mailto:[EMAIL PROTECTED] > + =========================================+ > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
