On Monday 03 October 2005 20:26, Upayavira wrote: > No, actually it is intended to fix the problem caused by a > URLStreamHandler already set by a containing application (e.g. servlet > container). Once you've got your own URLStreamHandler and have worked > around the VM's one, then you can just get on and solve the problems > that you were working on, and we (Cocoon and others) can happily embed > Felix within servlet containers, comfortable in the knowledge that we > can enjoy all of the benefits of your work on URLStreamHandlers without > any conflict with our container or any other apps running within it.
Besides the fact that you will likely to get VerifyError or something similar, and potentially have to deal with issues in collaboration between the java.net and the com.sun.net classes, don't you still need the container's classloader to be involved? All in all, I think Classloader tricks will hit back pretty badly. They normally do. What happened to the application isolation spec slated for JDK1.5?? Also, people who are more familiar with webapp containers... Are URLStreamHandlers really used in Tomcat, Weblogic, Websphere et al?? Or is this a hypothetical discussion? Cheers Niclas
