Hmm ... it appears that for some F***'ed up reason, that the URL created by using his.getClass().getResource() is no longer acceptable for TRAX when using Tomcat 4.1.18, as compared to Tomcat 4.0.4.
The problem is that the URI begins with a "/". If I remove that leading "/" suddenly the URLs are acceptable in Tomcat 4.1.18. Why would Tomcat be involving itself in such issues? Only thing I can think of is that maybe the conditions for this Apache Exception were redefined in 4.1.18: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Neal -----Original Message----- From: neal [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 11:02 AM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) I ported my app from Tomcat 4.0.4 (Windows) to Tomcat 4.1.18 (Windows) and now it doesn't work! It appears that I have a problem now with parsing my conf.xml file in my initServlet. I noticed that the new Tomcat has an "endorsed" directory with a different copy of Xerces in it. Is this somehow related? Here's the error: javax.xml.transform.TransformerException: org.apache.xml.utils.URI$MalformedURIException: No scheme found in URI Thanks. Neal --------------------------------------------------------------------- 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]