Hi all, While looking at the current XalanJ implementation, I could discover a bug as follows,
XML input document (test.xml): <test1> <val1>105</val1> </test1> XSLT stylesheet (test.xsl): <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="1.0"> <xsl:output method="xml" omit-xml-declaration="yes"/> <xsl:template match="/"> <xsl:call-template name="Test1"> <xsl:with-param name="a" select="test1/val1"/> </xsl:call-template> </xsl:template> <xsl:template name="Test1"> <xsl:param name="a"/> <xsl:value-of select="$a / 2"/> </xsl:template> </xsl:stylesheet> The above XSLT transformation, produces following result (when run as, java org.apache.xalan.xslt.Process -in test.xml -xsl test.xsl): SystemId Unknown; Line #15; Column #38; A relative location path was expected following the '/' or '//' token. SystemId Unknown; Line #15; Column #38; Extra illegal tokens: '2' 105 The XalanJ implementation should be able to determine, a concrete systemid (i.e the stylesheet location), that above mentioned error messages can display. I could fix locally, this bug, after which the above XSLT transformation produces error messages as follows, file:///d:/xslt/test.xsl; Line #15; Column #38; A relative location path was expected following the '/' or '//' token. file:///d:/xslt/test.xsl; Line #15; Column #38; Extra illegal tokens: '2' 105 I'm thinking to, prepare a new XalanJ 2.7.3 RC, with these improvements and make that available for review. On Wed, Sep 21, 2022 at 8:54 PM Mukul Gandhi <muk...@apache.org> wrote: > > Hi all, > We've produced a new XalanJ 2.7.3 RC here > https://dist.apache.org/repos/dist/dev/xalan/j/2.7.3/RC2/, after > incorporating a review comment that, the XalanJ project README should > contain detailed instructions on how to build a release for > distribution, and test the release before recommending that for > distribution. > > Please review, this RC. Great work everyone. Here's my +1 for this RC, > for XalanJ 2.7.3 release. -- Regards, Mukul Gandhi
