on 9/1/2000 12:32 PM, "Paul O'Leary" <[EMAIL PROTECTED]> 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.
turbine itself doesn't really "use" classloaders. The most that turbine does
is use Class.forName() and singleton's.
it is really up to the end person to understand CL basics...which
unfortunately, i admit really is black magic and sucks.
anyway, the TDK will place turbine.jar into the WEB-INF/lib directory by
default...ie: the context classloader. that should help people get a clue.
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
