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 / 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 exception wrappers... > > I've read some posts with complaints about the inability to use other XML > parsers. My problem is, I wouldn't mind using the standard xerces parser > that comes with tomcat 4.0 -- I just can't seem to get it to work... > > I'm assuming that I don't have to change anything in my tomcat installation > directory, but that I do have to provide some xslt libraries in my > webapps/webapp/WEB-INF/lib directory. > > Does anyone have an example configuration using xalan XSLT and Tomcat 4? > > Thanks for your help, > Brendan > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- +-------------------------------------------------------------------+ | Dave Makower <[EMAIL PROTECTED]> | | http://www.davemak.com/ | +-------------------------------------------------------------------+ -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
