I believe the classloader issue is actually related to how one's target
servlet engine loads classes. JServ and Tomcat do their own class
loading, and I believe can associate loaded classes with a specified
servlet context. I believe that Jon is saying that Turbine should
always be loaded through these servlet engine classloader hooks
(generally configuration files), rather than through the system
classpath.
Paul O'Leary wrote:
>
> I haven't really looked at how Turbine uses classloaders just yet - maybe
> that's my next project ;) - but the DBBroker's current singleton
> implementation relies on everything in the system referring to the same
> DBBroker class def so it'd have to be re-worked to go through a classloader.
> You're right, though, that seems like the right thing to do. Nice to have
> the ability to dynamically recycle all the class defs without having to tear
> down the VM as well.
>
> PaulO.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jon Stevens
> Sent: Friday, September 01, 2000 12:18 PM
> To: Turbine
> Subject: Re: Connections persisting across servlet engine restarts...?
>
> [snip]
>
> That is a very good point. My advice is to ALWAYS load Turbine in the
> context classloader, not the system class laoder.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
