DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18590>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18590 assert on subQueryResults->getDocumentOrder() == true in XPath.cpp, line 1408 Summary: assert on subQueryResults->getDocumentOrder() == true in XPath.cpp, line 1408 Product: XalanC Version: 1.4.x Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: XalanC AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The following XSLT fragment triggers an assert on subQueryResults->getDocumentOrder() == true in XPath.cpp, line 1408 <xsl:template match="MappingMerge"> ... <xsl:variable name="test1" select="MappingCache[1]"/> <xsl:copy-of select="$test1[1]"/> <!-- Here --> ... assuming a document like: <MappingMerge> <MappingCache> ... </MappingCache> ... </MappingMerge> With asserts turned off, the processing goes on as expected. The same stylesheet works fine with msxsl (4.0). Expressions like <xsl:copy-of select="$test1[2]"/> xsl:copy-of select="$test1[position()!=1]"/> etc. seem to work too. So it looks like it has to do with accessing the first element in a node set held by a variable.
