Another Xalan 2.2.D11 problem.

With the Lotus XSL 2.0.1 release the sample ApplyXSLT servlet properly found
the PI for the XSL to be applied to a given XML.  For example:

        <?xml version="1.0"?>
        <?xml-stylesheet type="text/xsl"
href="http://testsvr/xml/test.xsl";?>

would cause the "test.xsl" to be used for the transformation.  With Xalan
2.2.D11 this no longer appears to be true.  Instead a 500 error is reported
to the browser and the logs show:

        <BR>debug is false
        <BR>Parsing XML Document from PathInfo: /xml/test.xml
        <BR>Parsing XML Document from PathInfo: /xml/test.xml
        <BR>Performing transformation...
        <BR>javax.xml.transform.TransformerException:
org.xml.sax.SAXParseException: File "null" not found.</B>
        <BR>"
        
com.ibm.servlet.engine.webapp.WebAppErrorReport: <B>Exception occurred
during ctor/Transformation:
        <BR>debug is false
        <BR>Parsing XML Document from PathInfo: /xml/test.xml
        <BR>Parsing XML Document from PathInfo: /xml/test.xml
        <BR>Performing transformation...
        <BR>javax.xml.transform.TransformerException:
org.xml.sax.SAXParseException: File "null" not found.</B>
        <BR>

Specifying the XSL as a command line parameter works fine and is logged as:

        Parsing XSL Stylesheet Document from request parameter:
http://testsvr:80/xml/test.xsl

Peter Hunsberger

Reply via email to