Hi, I ended up playing for about six hours today trying to get the ClassLoader stuff working again today. There was a few issues. Namely that each time a resource was accessed it would reload, scan and build a JarFile and so on which was killing performance. There was also no way to specify permissions and a whole bunch of other stuff. Also we really can't take over the URL.setURLStreamHandlerFactory() because our hosted apps may want to use it.
So I started refactoring but really didn't come up with any ideas. I gotta say that I HATE the way they did protocol handling in the JVM though ;) Anyways there is only one thing that I haven't done yet that will probably work. It is ugly but the only option I can see ;( (Well other than writing our own ClassLoader which is probably heaps of work). Essentioally we have the code for the SarURLHandlerStream and friends in base classloader and in the system search path for that sort of stuff. We then have each thread store which current application it is dealing with and work that way. A bit ugly and britlle but it should work. -- Cheers, Pete -------------------------------------------------- Logic: The art of being wrong with confidence... -------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
