Which version of Xerces are you using? If it's 2.2, there is a bug
associated with the problem:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13282
-- Jeanfrancois
Mark R. Diggory wrote:
I keep getting these parsing exceptions when I try to load my custom
taglibs (from JAR files) on
Here's my environment:
j2sdk 1.4.0
Ant 1.5.1
tomcat LE 4.1.12
I have no idea which implementation of Xerces it is using out of these
installations. But these are the only locations that I think Xerces is
getting picked up from are Ant and j2sdk. I though j2sdk used Crimson?
thanks,
-Mark
I keep getting these parsing exceptions when I try to load my custom
taglibs (from JAR files) on Tomcat 4.0.3, 4.0.5, 4.1 on Windows 2000/XP.
Starting service Tomcat-Standalone
Apache Tomcat/4.0.3
PARSE error at line 1 column -1
org.xml.sax.SAXParseException: Character conversion error:
Well, I installed 4.0.3 regular version instead of LE, now I assume I
should be using the Xerces parser thats part of tomcat, but I still get
the exceptions. Since j2sdk has its own installation of an xml parser
(Crimson, go figure which Moron came up with the idea to default package
a buggy
Tag Library on Microsoth Windoz
Well, I installed 4.0.3 regular version instead of LE, now I assume I
should be using the Xerces parser thats part of tomcat, but I still get
the exceptions. Since j2sdk has its own installation of an xml parser
(Crimson, go figure which Moron came up with the idea
If you access your XML parser through the JAXP APIs (which Tomcat does for
its own use), there is a standard and portable mechanism for selecting the
parser implementation to be used -- see the JAXP specification for
details.
Craig McClanahan
No, this has to strictly deal with default
: Can't deploy Custom Tag Library on Microsoth Windoz
If you access your XML parser through the JAXP APIs (which Tomcat does for
its own use), there is a standard and portable mechanism for selecting the
parser implementation to be used -- see the JAXP specification for
details.
Craig
Craig R. McClanahan wrote:
I've tried numerous encodings in my tld file, it always says UTF-8 even when I'm not
encoded in UTF-8. It was pointed out that this is a bug in an old version of Xerces.
But, when I install LE versions, I'm not using Xerces, I'm using the default Crimson
parser in
Are you testing on Windows with j2sdk1.4?
Craig R. McClanahan wrote:
Works for me with no problems on all 4.0.x and 4.1.x versions of Tomcat;
but I'm not trying to use any UTF-8 characters in my TLDs either.
Craig
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional
Custom Tag Library on Microsoth Windoz
Are you testing on Windows with j2sdk1.4?
Among other combinations, yes.
Beyond my own use, anybody using the Java Web Services Developer Pack
(JWSDP) download from Sun is doing exactly this as well, since it's based
on an earlier 4.1 version of Tomcat
When I was working with LE versions of Tomcat I believe it was
defaulting to whatever is in j2sdk1.4.0. I think this is Crimson, only
because the code for Crimson is in the src.zip of j2sdk. What I saw with
that was the following parsing error:
PARSE error at line 1 column -1
This doesn't seem to happen with the standard.jar and I'm totally
copying its layout and the version information at the beginning of the
file accept for the encoding being UTF-8 instead of ISO...
Well, I notice that the standard jar also stores the files under thier
own names and not
12 matches
Mail list logo
