Let me rephrase the question, how does Tomcat determine what is a session attribute. What if there are classes that implement java.io.Serializable that have nothing to do with "session attributes?"
-ryan -----Original Message----- From: J. Ryan Earl [mailto:[EMAIL PROTECTED] Sent: Friday, April 22, 2005 10:19 AM To: Lionel Farbos; Tomcat Users List Subject: RE: Clustering "application scope replication" I've read that document many times, and that does not answer my question. -ryan -----Original Message----- From: Lionel Farbos [mailto:[EMAIL PROTECTED] Sent: Friday, April 22, 2005 9:50 AM To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: Re: Clustering "application scope replication" As it is explained in the doc : "All your session attributes must implement java.io.Serializable" On Fri, 22 Apr 2005 09:44:01 -0500 "J. Ryan Earl" <[EMAIL PROTECTED]> wrote: > How does Tomcat know what to serialize? Does it just use the Reflection > package and serialize out -everything- that implements java.io.Serializable? > > -ryan > > -----Original Message----- > From: Lionel Farbos [mailto:[EMAIL PROTECTED] > Sent: Friday, April 22, 2005 9:11 AM > To: Tomcat Users List > Cc: [EMAIL PROTECTED] > Subject: Re: Clustering "application scope replication" > > > Hi > > For your needs, you can use > session replication > (http://jakarta.apache.org/tomcat/tomcat-5.5-doc/cluster-howto.html) > or > your own mechanisms and tables with datas in a database ... > Regards. > > On Fri, 22 Apr 2005 15:15:54 +0200 > "Joakim Ahlén" <[EMAIL PROTECTED]> wrote: > > > Ok, too bad. Is there any way of storing objects if we want them in > "cluster scope"? > > > > An ugly hack would be to use one single HttpSession with a special > session-id to store global objects, and somehow fetch objects from within > this HttpSession from inside requests that belongs to other sessions. I > can't see how this could be done though, since request.getSession() can't > fetch other sessions than its own. This would probably also have to include > some tomcat specific magic which i wouldn't want. > > > > Any help is appreciated on how to handle this problem! > > > > Thanks > > > > Joakim > > > > On Fri, Apr 22, 2005 at 08:07:21AM -0500, Jess Holle wrote: > > > The servlet spec says this data is local to a given JVM. > > > > > > I suppose a servlet engine could expand beyond the spec, but I'd be > > > surprised if Tomcat did here. > > > > > > Joakim Ahlén wrote: > > > > > > >Hi! > > > > > > > >We have a cluster of two tomcat 5.5.9-machines using session > replication. > > > >However, we also have data in application scope (set with > > > >getServletContext().setAttribute(...)) which as far as i have found in > the > > > >docs, is not replicated. > > > > > > > >Is there any way to accomplish this with tomcat? If not, is there any > plan > > > >to develop support for it? Do other application servers have support > for > > > >this? > > > > > > > >Hope you can help me. > > > > > > > >Regards > > > > > > > >Joakim > > > > > > > >--------------------------------------------------------------------- > > > >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] > > > > > > > --------------------------------------------------------------------- > > 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] > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
