On Mon, 26 Nov 2001, Mika Goeckel wrote:
> Date: Mon, 26 Nov 2001 15:05:27 +0100
> From: Mika Goeckel <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]>
> Subject: Re: 4.0.1 ClassLoader b
On 25 Nov 2001, Kevin A. Burton wrote:
> Date: 25 Nov 2001 21:20:09 -0800
> From: Kevin A. Burton <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: 4.0.1 ClassLoader breaks singletons on webapp reload.
>
> -BEGIN PGP SIGNED MESSAGE
cording 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 singl
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 chang
[EMAIL PROTECTED] (Kevin A. Burton) writes:
> Jon Stevens <[EMAIL PROTECTED]> writes:
>
>> Sadly, I have to admit that the Turbine Services framework shutdown
>> code is currently broken and has been for some time now...it needs
>> to be re-written...
>
> Are you saying that the theory is broken
--- "Kevin A. Burton" <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> So what patterns do developers follow when the want
> to deploy webapps with
> singletons that have support for reloading?
>
> Kevin
You have a couple of basic strategies for having
'part'
ECTED]>
Sent: Monday, November 26, 2001 8:52 AM
Subject: Re: 4.0.1 ClassLoader breaks singletons on webapp reload.
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jon Stevens <[EMAIL PROTECTED]> writes:
>
> > on 11/25/01 9:57 PM, "Remy Maucherat" <[EMAI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Stevens <[EMAIL PROTECTED]> writes:
> on 11/25/01 9:57 PM, "Remy Maucherat" <[EMAIL PROTECTED]> wrote:
>
> > Of course, there's a reason for this, as a selective reloading would be a
> > very complex thing to do.
> >
> > Remy
>
> More like dam
> "Remy Maucherat" <[EMAIL PROTECTED]> writes:
>
> > > OK.
>
>
> > No. Of course, there's a reason for this, as a selective reloading
would be a
> > very complex thing to do.
>
> So what patterns do developers follow when the want to deploy webapps with
> singletons that have support for reloadi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Remy Maucherat" <[EMAIL PROTECTED]> writes:
> > OK.
> No. Of course, there's a reason for this, as a selective reloading would be a
> very complex thing to do.
So what patterns do developers follow when the want to deploy webapps with
singletons
on 11/25/01 9:57 PM, "Remy Maucherat" <[EMAIL PROTECTED]> wrote:
> Of course, there's a reason for this, as a selective reloading would be a
> very complex thing to do.
>
> Remy
More like damn near impossible. Once the previous classloader has been
trashed, all objects which were created within
> OK.
>
> I have a webapp deployed with the main package under WEB-INF/classes and
all
> dependent libraries under WEB-INF/lib as .jars.
>
> If I recompile my application, update the necessary classes in
WEB-INF/classes,
> Tomcat does manage to reload the app but my application is now totally
hose
12 matches
Mail list logo
