Christopher, "Christopher K. St. John" wrote: > That seems a bit hostile. The majority of stuff that could > go into /ext is harmless. Ignoring it punishes users who > correctly install the "right" extensions.
You have a good point. Using "-Djava.ext.dirs=" is an all or nothing approach and may be too limiting. > My proposal was based on idea that if you can't solve a > hard-to-diagnose problem, you ought to at least make it > obvious. I'd be worried that ignoring /ext solves one > such problem but replaces it with another. I can't help but think that there might be a way to point Tomcat to its bundled jars without losing access to any non-conflicting extensions. Since Tomcat constructs its own class loader to load its bundled jars (including servlet.jar), one possible solution would be to set the "-Djava.ext.dirs=" in the scripts and then have the class loaders in Bootstrap.java add the jars in the JVM's jre/lib/ext directory to the end of its search list. This way, any conflicting extensions would be loaded after the bundled jars. We use a similar mechanism to work around the endorsed dirs mechanism with JDK 1.4. Does this seem to have potential? If it works, Tomcat would be able to isolate itself from conflicting extensions (i.e. we could eliminate the problem instead of just printing an error message) while still accessing the installed extensions (e.g. JSSE, etc.). Patrick -- _____________________________________________________________________ Patrick Luby Email: [EMAIL PROTECTED] Sun Microsystems Phone: 408-276-7471 901 San Antonio Road, USCA14-303 Palo Alto, CA 94303-4900 _____________________________________________________________________ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
