Mukul Gandhi created XALANJ-2638:
------------------------------------
Summary: error reporting improvement, for XalanJ interpretive
processor for few of XPath parse errors, during XSLT transformation
Key: XALANJ-2638
URL: https://issues.apache.org/jira/browse/XALANJ-2638
Project: XalanJ2
Issue Type: Improvement
Security Level: No security risk; visible to anyone (Ordinary problems in
Xalan projects. Anybody can view the issue.)
Components: parse-or-compile
Affects Versions: 2.7.2
Reporter: Mukul Gandhi
Assignee: Mukul Gandhi
Fix For: 2.7.3
Here's an illustration of this issue.
XML document:
<test1>
<val1>105</val1>
</test1>
XSLT stylesheet:
<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 mentioned, XSLT transform produces, following errors using XalanJ
2.7.2 interpretive processor,
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 fix for this, issue should produce, the actual value of systemid within
such error messages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
