Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Bizarre parse error
Date: Tue, 22 Jun 2004 14:44:42 -0400
Message-ID: 
 <E8CC5F35918C084F8DBF32A5161C40030117C185@mailserver.basistech.net>
Thread-Topic: Bizarre parse error
Thread-Index: AcRYiHdYeegM/0z3TjeLC3A07TJ9GQAABMDA
From: "Benson Margulies" <bim2004@basistech.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>

Here's what I've seen.

The TRaX API, as implemented by xalan, has a thing called
javax.xml.transform.stream.StreamResult.

The xalan implementation of this looks at the type of the object passed
in to decide what sort of character handling is desired.

When you pass in a JspWriter, it gets confused, because JspWriter is not
one of the fixed set of classes that were wired into the xalan source as
of the time I read the xalan source.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org