Sorry to nose in, but: 1) Can't you work around this by passing in URLStreamHandlers in the URL constructor? 2) If you supplant the Tomcat URLStreamHandler with your own, would it interfere with some jndi stuff (In TC 4, I seem to remember the catalina URLStreamHandlers getting your web app resources)?
Benjamin J. Armintor Operations Systems Specialist ITS-Systems: Mainframe Group University of Texas - Austin tele: (512) 232-6562 email: [EMAIL PROTECTED] -----Original Message----- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 9:58 AM To: Tomcat Users List Subject: Re: URL.setURLStreamHandlerFactory - Tomcat 5.0 On Wed, 11 Aug 2004 08:55:34 -0400, Shapira, Yoav <[EMAIL PROTECTED]> wrote: > Hi, > It's funny you should ask now, just as I was contemplating > http://issues.apache.org/bugzilla/show_bug.cgi?id=29631. I think I'm > going to implement that in the coming days, probably via a system > property (a bit ugly, but this is enough of a marginal feature that I > can live with it being ugly for now). However until that happens, the > answer to your question is no: the setURLStreamHandlerFactory call > cannot be avoided with current Tomcat releases. You must build a > custom Tomcat to do that. Since setURLStreamHandlerFactory is a one-per-VM type call, it is not justifiable to require using that anywhere in user applications. I'm ok if you want to allow extending the Tomcat stream handler a little, but I used to resolve this report with WONTFIX. R�my --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
