Hi, We figured out the problem - moving xalan.jar, xercesImpl.jar, and xml-apis.jar into the jdk's jre/lib/ext directory meant that we didn't have to include them explicitly in any classpaths, and the "self-registration" as service providers seemed to work. Before, the files were in a directory outside the jdk, and included manually in the application's classpath.
Eric :-----Original Message----- :From: Eric R. Rath [mailto:[EMAIL PROTECTED] :Sent: Tuesday, May 21, 2002 12:04 PM :To: xalan-j-users :Subject: problem with Xalan 2.3.1 jar? : : :Hi, : :I've been using an older version of Xalan (pre-2.2D14) with no :problems on a :Linux machine with Apache, Jserv, and Xerces. Because I'm not sure which :version of Xalan (or Xerces) I've been using (I didn't set it up), I tried :to upgrade to Xalan 2.3.1, and the version of Xerces that ships with it. : :I put xalan.jar, xercesImpl.jar, and xml-apis.jar into the :classpath for the :application, and tried to start it up. When the application first tries to :call TransformerFactory.newInstance(), I get the following message: : :[21/05/2002 09:44:54:103] (ERROR) ajp12: Servlet Error: :javax.xml.transform.TransformerFactoryConfigurationError: Provider for :javax.xml.transform.TransformerFactory cannot be found: Provider for :javax.xml.transform.TransformerFactory cannot be found : :I'm pretty sure that jserv is finding all the jars, as it complains when a :jar cannot be found. I also checked that the new xalan.jar and xerces.jar :included the service provider configuration files, and that they were :correct; everything looked okay. : :I haven't seen anyone else with this problem, so it seems unlikely :that this :is a problem with the xalan or xerces jars, but then again, the only thing :that changed were the jars. Does anyone have any suggestions for things to :check that I might be doing wrong? : :Eric
