That's normal. The full URL should look soemthing like this, though...
file:///D:/dev/tomcat/webapps/myapp/WEB-INF/classes/org/mypackage/somefile.properties
or if it is inside an archive...
jar:file:///D:/dev/tomcat/webapps/myapp/WEB-INF/lib/somejar.jar!/org/mypackage/somefile.properties
Jake
At 01:00 PM 3/1/2003 -0800, you wrote:
Actually,
It seems that the problem is that Class.getResource() is returning a URL with a leading "/" dispite the fact that I'm on a Windows box. For instance, its returning a url like:
/D:/dev/tomcat/...
where it *should* be returning:
D:/dev/tomcat/..
If I mockup a String of that nature it works fine which seems to confirm this.
So, I could always compensate by removing the "/" but I ultimately deploy to Linux and I presume this will mess up my paths in my production site if I do so.
Of course, I could always find a workaround ... but ... should I have to? I mean, I'm guessing this is a bug somehow associated with the context of this version of Tomcat.
Any thoughts?
Thanks.
Neal
-----Original Message----- From: Reynir Hübner [mailto:[EMAIL PROTECTED] Sent: Saturday, March 01, 2003 12:41 PM To: Tomcat Users List Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
Hi,
This may have something to do with an upgraded version of jaxp or xerces, distributed with some dists of tomcat. According to the error you're getting your url is missing scheme, often 'http' or 'https' in the beginning of the url (before '://')
[scheme:]scheme-specific-part[#fragment]
Which version of tomcat did you download (the full version or 1.4. LE) ?
Hope it helps -reynir
> -----Original Message----- > From: neal [mailto:[EMAIL PROTECTED] > Sent: 1. mars 2003 20:36 > To: Tomcat Users List > Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4) > > > 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] > >
--------------------------------------------------------------------- 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]
