On Mon, 7 Oct 2002, Mark R. Diggory wrote:
> Date: Mon, 07 Oct 2002 14:45:15 -0400
> From: Mark R. Diggory <[EMAIL PROTECTED]>
> Reply-To: Tag Libraries Developers List <[EMAIL PROTECTED]>
> To: Tag Libraries Developers List <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: Can't deploy Custom 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 to default package
> a buggy xml parser into the j2sdk and then force us to configure some
> stupid config buried inside the jdk installation just to get out of it.
> What up with that Sun!).
>
> Is there a way I can configure tomcat to use a different XML parser
> without messing around in the jdk?
>
> Hey Sun, if your listening! I don't want the jdk to set a "default XML
> parser", I would never want jdk to set a "default xml parser". Its
> "Always" the case that I want to use "MY SELECTED XML PARSER" never
> never never would I want it to "JUST DEFAULT to some parser that I've
> never used before in my life", expecially one that is buggy!
>
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.
> -Mark
Craig McClanahan
>
> Mark R. Diggory wrote:
>
> > 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: "Malformed
> >> UTF-8 char
> >> -- is an XML encoding declaration missing?" (line number may be too
> >> low).
> >> PARSE error at line 1 column -1
> >> org.xml.sax.SAXParseException: Character conversion error: "Malformed
> >> UTF-8 char
> >> -- is an XML encoding declaration missing?" (line number may be too
> >> low).
> >> PARSE error at line 1 column -1
> >> org.xml.sax.SAXParseException: Character conversion error: "Malformed
> >> UTF-8 char
> >> -- is an XML encoding declaration missing?" (line number may be too
> >> low).
> >> PARSE error at line 1 column -1
> >> org.xml.sax.SAXParseException: Character conversion error: "Malformed
> >> UTF-8 char
> >> -- is an XML encoding declaration missing?" (line number may be too
> >> low).
> >> PARSE error at line 1 column -1
> >> org.xml.sax.SAXParseException: Character conversion error: "Malformed
> >> UTF-8 char
> >> -- is an XML encoding declaration missing?" (line number may be too
> >> low).
> >> PARSE error at line 1 column -1
> >> org.xml.sax.SAXParseException: Character conversion error: "Malformed
> >> UTF-8 char
> >> -- is an XML encoding declaration missing?" (line number may be too
> >> low).
> >> No tags
> >> No tags
> >
> >
> >
> > I know this is coming from some parsing error when the tld is parsed.
> > But even if I put the tld file into different encodings (ISO-8859-1).
> > I still get the exceptions.
> >
> > example tld header:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <!DOCTYPE taglib PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag
> > Library 1.2//EN"
> > "http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd";>
> > <taglib>
> > ...
> >
> > -Mark Diggory
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> >
>
>
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
