Gary,
I'm including the environment info at the end of the message. However,
with Gulli's help I was able to fix the problem. It turned out, all I had
to do was to move xalan.jar out of ${tomcat_home}/lib and into
${web_app}/web-info/lib. I hope, this is an appropriate fix.
Thanks
Dmitry
#---- BEGIN writeEnvironmentReport($Revision: 1.5 $): Useful properties
found: ----
java.version=1.3.0
#---- BEGIN Listing XML-related jars in: foundclasses.java.class.path ----
xerces.jar.apparent.version=xerces.jar potential-ERROR present-unknown-version
xerces.jar.path=C:\jakarta-tomcat-3.2.2\bin\..\lib\xerces.jar
#----- END Listing XML-related jars in: foundclasses.java.class.path -----
version.JAXP=1.1
java.ext.dirs=c:\javasoft\jre\1.3\lib\ext
version.crimson=not-present
java.class.path=..\classes;..\lib\ant.jar;..\lib\jasper.jar;..\lib\servlet.jar;..\lib\webserver.jar;..\lib\xerces.jar
version.xerces=Xerces 1.4.2
sun.boot.class.path=c:\javasoft\jre\1.3\lib\rt.jar;c:\javasoft\jre\1.3\lib\i18n.jar;c:\javasoft\jre\1.3\lib\sunrsasign.jar;c:\javasoft\jre\1.3\classes
version.DOM.draftlevel=2.0fd
version.xalan2=Xalan;Java;Xalan Java 2.2.D8;
version.DOM=2.0
version.xalan1=not-present
#----- END writeEnvironmentReport: Useful properties found: -----
# YAHOO! Your environment seems to be OK.
At 10:08 PM 8/11/2001, you wrote:
>Dmitry --
>
>All current versions of XalanJ2 should be using the correct Tomcat class
>loader. Please provide details as to the directory where xalan.jar is
>located and and the directory where the extension is located. What
>version of XalanJ are you using? What version of the JDK are you
>using? What error message are you receiving (with stack trace if
>possible).
>
>Also, in your servlet, please include the following line just before
>kicking off the transformation:
>
>boolean environmentOK = (new
>EnvironmentCheck()).checkEnvironment(yourPrintWriter);
>
>and let us know what the output is from there.
>
>Thanks,
>Gary
>
>
>Dmitry Beransky wrote:
> >
> > Hi,
> >
> > I've finally managed to search the list archives with google (the archive
> > page is still unaccessible) and I've noticed that a few people had reported
> > the problem of Xalan not finding classes for extension functions/elements
> > before and someone was looking into this issue. Unfortunately, whatever I
> > recovered from google was incomplete and I couldn't find out how this all
> > ended.
> >
> > I'd appreciate if someone would summarize the state of the issue. I've
> > looked through the code and believe that the problem results from a bug in
> > Xalan, but I'd like to hear from someone in the knows before I jump to any
> > conclusions.
> >
> > Best regards
> > Dmitry
