Comparing 2 variables in XSLT

mralexk · January 8th, 2016, 01:59 PM

I am having an issue with following XSLT code:

<xsl:when test="$myissueNum=$mySWRissueNum">
<xsl:for-each select="./elements/element">
<xsl:variable name="myfile" select="./@location" />

<xsl:value-of select="$myfile"/><br/>
</xsl:for-each>
<br/>
</xsl:when>

I tried to use IF statement instead with the same result. Basically it is error out on comparing one variable to another variable. If I change right variable to a value, it will start working, but unfortunately I do need both variables to stay variables because this code is with it another loop.

<xsl:for-each select="/report/acResponse/issues/issue">
<xsl:variable name="myissueNum" select="./issueNum" />

That loop basically goes through the list of issueNum

And that look within another loop:

<xsl:for-each select="/report/SWRINFO/issues/issue">

which goes through mySWRissueNum.

This suppose to create a table. A list of files that belong to a specific issue and that table is within another table, the list of issues. Each issue has the list of files.
I am not quiet sure how to make this work. This code worked just fine in Internet Explorer 9 but in IE 11 it is no longer working.

If I remove that when function, it shows style of xml fine, but there is no list of files shown for each issue. The XML generated automatically from 3rd party tool. I don't have much control over XML format. The XSLT should work with XML created for any type of issues in the tool.

mhkay · January 8th, 2016, 03:46 PM

What error message do you get?

mralexk · January 8th, 2016, 05:07 PM

There is no error message in IE 11. It just show some data, not completely, but without format. Kind of in one line. In Firefox it shows this error: "Error during XSLT transformation: An unknown error has occurred ()".
I know for sure that this particular Chose When function is failing, because if I remove it, entire page shows up just fine. But that particular function is gone, which makes entire page kind of obsolete. The only reason that report generated is to show dependency of files and issues.
I am now trying to work on alternative way to show the data, as I can't find the way to make it work with XLST, but that may take a while.

mhkay · January 8th, 2016, 05:57 PM

You never mentioned that you were running in the browser. That's the worst possible place to test XSLT code, but if you have to, then running XSLT with the Firefox debugging environment enabled can work reasonably well. But it's years since I've done it, so I can't help on the details.