Hey
"Jung , Dr. Christoph" wrote:
> >Yes and no. Depends. If the file connection is cached while it's
> >deployed, then the tmp-copy is still needed. If the connection is closed
> >on each usage, then it would be possible to skip the tmp-copy.
>
> I thought on something like: when the classloader is garbage-collected (or
> even
> called a dedicated finalize() explicitely), the yet open file connections
> are closed
True.
> >Yes, it would be very painful. Doing search/replace on URLClassLoader to
> >FixedClassLoader will probably take, well maybe a minute. Noone probably
> >has the time to do that soo....
> >;-)
>
> But you couldn´t do search and replace in external stuff, like Tomcat
> sources, could you?
Don't have to, since Tomcat doesn't use UCL in the first place.
> It is clear that we need the UCL code at least at classloader construction
> time. The question was whether we shouldn´t pass the references as
> "java.lang.ClassLoader"
> afterwards (at least it would show us places where we heavily depend on
> URLClassLoader and where not)?
Sure, but that's what we do now. (or am I missing something here??)
regards,
Rickard
--
Rickard Öberg
Email: [EMAIL PROTECTED]
