Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of bimargulies@gmail.com
 designates 209.85.219.216 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=fNki+1e7IcZJ5ls/xVS6/6n4givi2Iyy5TWi8QVLtYs8oXLcsw/Ps+gAif42ZGIHba
         IZscYN+Pk5Pgc29OJqcJ2XO1bQEEZ2CbQhZaouSfadQfMJwuGAsWyEynAF32FU8Cp0Kw
         t9buHGBC3CmfytSLTsFRxjEbnCU+g5R2u8jII=
MIME-Version: 1.0
Date: Tue, 3 Nov 2009 07:12:18 -0500
Message-ID: <61b5d9410911030412h7deb5830va97839220408404@mail.gmail.com>
Subject: Tomcat Xalan classpath problem
From: Benson Margulies <bimargulies@gmail.com>
To: users@tomcat.apache.org
Content-Type: multipart/alternative; boundary=0016e6d77d12d3c3750477766731

--0016e6d77d12d3c3750477766731
Content-Type: text/plain; charset=UTF-8

I have a webapp that makes calls to the JAXP 1.4/Java 1.6 APIs that allow
the caller to pass in the class name of implementation classes.

It all works find standalone. It works fine in Jetty. It fails in Tomcat
6.0.20. The error is a missing method in a Xalan class; as if Tomcat has
somehow gotten an older version of Xalan into the classpath.

I don't see any likely suspects in the Tomcat tree, so I'm momentarily
mystified.

--0016e6d77d12d3c3750477766731--