xml - xsl:sort inside for-each-group() -
for reason xsl:sort inside for-each-group throwing exception since upgrading saxon 9.7.0.1
xml-
<table class="vv"> <tr><td>woot1</td><td>woot2</td></tr> <tr><td>woot1</td><td>woot2</td></tr> <tr><td>woot1</td><td>woot2</td></tr> <tr><td>woot1</td><td>woot2</td></tr> </table> xsl-
<xsl:template match="/"> <xsl:apply-templates/> </xsl:template> <xsl:template match="table[@class='vv']"> <div class="row"> <xsl:for-each-group select="tr" group-by="td[1]/text()"> <xsl:sort/> test </xsl:for-each-group> </div> </xsl:template> error-
just want verify if bug in saxon or got changed way used work in xslt 3.0
an incompatibleclasschangeerror means there's class loaded jvm @ run-time different way looked @ compile time. is, code compiled classpath included different version of library class version has been loaded @ runtime.
two possible theories investigate:
(a) in case, on face of it, classes involved seem saxon classes, might suggest have more 1 version of saxon on classpath, , reason code being loaded both.
(b) on other hand, can see right @ bottom of screenshot, half-cropped, line suggests using saxon-ee byte-code generation enabled, , might indicate bug in byte-code generation. try disabling byte-code generation see if problem goes away. example calling processor.setconfigurationproperty(featurekeys.generate_bytecode, false).
if turn out bytecode generation bug, please log @ http://saxonica.plan.io, can track properly. need access stylesheet demonstrates problem.

Comments
Post a Comment