We had exactly the same problem. Turns out it's a known bug (or perhaps
"mis-feature") in Tomcat 4.0.3. We downloaded 4.0.4b1, and it worked again
without us having to change anything in our code.
On 3/17/02 9:54 AM, "Brendan Colthurst" <[EMAIL PROTECTED]> wrote:
>
> I had a simple XML / XSL
Tomcat User List,
Okay, I always do this -- post a problem, then post the solution...
I just had to:
1. Download the source for the xalan package:
http://xml.apache.org/dist/xalan-j/xalan-j_2_3_1-src.tar.gz
2. Remove their xercesImpl.jar
3. Replace it with the xerces.jar that came with tomcat.
I had a simple XML / XSLT transform utility working with tomcat 3.2.3
using the xalan and xerces libraries.
I upgraded to tomcat 4.0.3, and now the utility throws configuration
exceptions. I'm having trouble getting the details of the exceptions
because they're all wrapped up in servlet except