MK <kaeppler.matthias <at> nts.ricoh.co.jp> writes: > [...] > I am using Tomcat 5.5 by the way. > > I will try rolling a jar from my protocol handler and put it in the places you > suggested. Maybe that'll work, I'll report back.
actually I just realized that this is not gonna help if Tomcat does not honor the java.protocol.handler.pkgs setting, because even if Tomcat can load the JAR and knows where to look for it, it would still need to read this setting to load the Handler class upon URL construction (because this happens through Tomcat's URLStreamHandlerFactory), no? Anywho, I just tried common/lib, common/endorsed and a custom location I added manually to the classpath (which would make it available to the system classloader right?). Didn't work. Any ideas left that do not include the words "Tomcat sources" and "modify"? :D I still can't quite believe how a trivial operation such as constructing a java.net.URL from a wellformed (!) URL can cause so much trouble in a Servlet based environment. I must be missing something. Regards, Matt --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
