Howdy,
This whole thread might be related to other one, regarding your
upgrade method of simply copying over. You may end up with
mismatching internal tomcat jars.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: neal [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 01,
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
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
Hmm ... I'm wondering how this is going to affect the x-platform-ness of my
application now.
I'm developing on a windows platform and deploying to linux, wherein my
paths actually *should* start with a /.
UUugh.
-
To
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]
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
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
If that's normal then why did it work in Tomcat 4.0.4 and not in Tomcat
4.1.18?
I can not say positively that it was not adding that leading slash in 4.0.4
but it was the first thing I noticed and when I took it out it fixed the
problem.
What else could it be?
Neal
-Original Message-
actually the full URL that's coming back does not have the file:// in
front. I guess that's why its complaining about not having a scheme.
But again, why did it work before? Why does it not work now? And if the
scheme is required, why is Class.getResource() not returning that as part of
the
First, how how exactly are you calling getResource()? Here are some
examples...
This will get the resource in the root of the current classloader ( ie...
WEB-INF/classes or the root of a .jar file)
myClass.getResource(/myprops.properties);
This will get the resource relative to the location
On Sat, 1 Mar 2003, neal wrote:
Date: Sat, 1 Mar 2003 13:29:08 -0800
From: neal [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
actually the full URL that's coming
Hmm. I hear what you're saying but I would think that if Tomcat uses
different forms of URL formats that would be a fundamental
backwards-compatability issue. Is this not a concern of the product?
:(
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]
Sent:
On Sat, 1 Mar 2003, neal wrote:
Date: Sat, 1 Mar 2003 13:59:27 -0800
From: neal [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: XML problem with Tomcat 4.1.18 (but was ok in 4.0.4)
Hmm. I hear what you're saying but I
Thanks for the info.
I guess I'm just frustrated because my app broke when I upgraded Tomcat.
:-\
Neal
-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 01, 2003 4:36 PM
To: Tomcat Users List
Subject: RE: XML problem with Tomcat 4.1.18 (but was
14 matches
Mail list logo
