tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cox, Charlie" <c...@cincom.com>
Subject RE: [next] What's next ?
Date Thu, 02 Oct 2003 17:59:55 GMT


> -----Original Message-----
> From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
> Sent: Thursday, October 02, 2003 11:57 AM
> To: Tomcat Developers List
> Subject: RE: [next] What's next ?
> 
> 
> 
> Howdy,
> 
> >> 2. Eliminate the shared and common classloader 
> repositories.  Unless
> >> these are required by the spec?  Force webapps to be self-contained
> by
> >> putting all their classes in WEB-INF/lib or 
> WEB-INF/classes of their
> >> webapp.  Have the WEB-INF/clases -> WEB-INF/lib -> 
> endorsed -> system
> >> classloader hierarchy, much simpler than current.
> >
> >I believe many people won't like that one. It's quite 
> radical :) It is
> >true that it would be much simpler to run only "straight" webapps,
> >without exceptions.
> >
> >I think this kind of classloading structure can be configured in TC 5
> >using the catalina.properties.
> 
> If it can be achieved via configuration, I'm happy ;)  How can it be
> done?
> 
> Vis a vis native libraries and reloading -- I didn't have 
> that scenario
> in mind.  I don't know what to do about that one.  So what 
> you're saying
> is there's no way to deploy a self-contained webapp (everything under
> the webapp root), and be able to restart it without restarting the
> server, if you're using a native library in your webapp?
> 

yes, that's it. Once you drop the classloader that holds the library
reference, you can no longer access the library and can not load it
again(error:'library already loaded in another classloader'). 

Charlie

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message