On Tue, 30 Oct 2001 06:10, Stefano Mazzocchi wrote: > > However everytime I tried to implement this I ended up with a spiderweb > > of ugly dependenceis and assumptions - not really maintainable. > > > > It also required us to set per JVM protocol factory because the class > > implementing SarURLStreamHandler was not in system classloader but in the > > containers classloader. > > Hmmm, what if we design a new URL-handling system that cascades back on > the JVM one directly into avalon? Cocoon already does this, but as more > and more things require to properly setup protocol handlers, this might > be a thing to consider.
I tried that but the problem is jar:sar:/SAR-INF/lib/foo.jar!/org/apache/avalon/Foo.class I can make the "jar:" part of URL use our abstraction but as soon as it goes to lookup the nested URL "sar:/SAR-INF/lib/foo.jar" it will use the system loader which will break ;( > > * ignoring this factor and always extracting lib > > * something else? > > having a thread-group and one main thread per SAR is not that bad of an > idea. After all, this is what you expect when you have multiple servers > running inside the same JVM. tried that but a few peoples complained. May make it optional in future. The reason people complained was that they were embedding Phoenix into a GUI and separate ThreadGroups + safe handoffs were causing much more higher resources use. -- Cheers, Pete -------------------------------- My opinions may have changed, but not the fact that I am right -------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
