?? Don't understand that joke. EJB's are usually not singletons. An application server may decide how many instances it creates in the case of stateless session beans, so he may choose to only create one, but most commercial servers (weblogic, websphere) adjust the number of beans according to the traffic (concurrent sessions).
Could you clarify that? Mika ----- Original Message ----- From: "Jon Stevens" <[EMAIL PROTECTED]> To: "tomcat-dev" <[EMAIL PROTECTED]> Sent: Monday, November 26, 2001 10:04 PM Subject: Re: 4.0.1 ClassLoader breaks singletons on webapp reload. > Yea, those are called EJB's. :-) > > EJB - The glorified Singleton. > > -jon > > > on 11/26/01 6:05 AM, "Mika Goeckel" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > could you get around the singleton problem by placing the singleton object's > > class outside the classloader which get busted when reloading the changed > > servlets/jsps? You could move it up to the 'shared' or even 'common' > > classspace. Do I understand it right, that these class loaders are not being > > destroyed when TC is running? I'm not so deep into that matter, maybe I > > completely misunderstand something... > > > > Mika > > > -- > 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]>
