Holding and changing a variable in XSLT

[aidy]

Hi,

This is a snippet of my XSLT

<xsl:for-each select = "SAFS_LOG/LOG_MESSAGE">
<xsl:choose>
<xsl:when test="@type = 'FAILED'">
<xsl:variable name="isFailed" select="@type" />
<BR> "FAILED" </BR>
</xsl:when>

<xsl:when test="@type = 'END DATATABLE'">
<xsl:if test = "not('FAILED'=$ isFailed)">
<BR> "PASSED" </BR>
</xsl:if>
</xsl:when>

</xsl:choose>
</xsl:for-each>

I am looping an XML file. If I get an attribute named 'type' with a
value of 'FAILED',
I would like to assign that value to a variable, then in the next
conditional statement
if that variable does not contain the value 'FAILED', I would like to
create a pass.

However, when I run the tansform, I receive a variable not resolved or
defined error.

Could you please help?

Aidy

[Joe Kesselman]

A variable is "visible for all following siblings and their
descendants." That basically means you can't return it to a higher level
of the stylesheet, even within a single template.

The simplest fix is to invert the problem. Do your testing to calculate
the value of the variable rather than using the test to control how it
gets set, so the variable definition is a top-level child of the
template and thus is visible to everything following it in the template.

--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry

[aidy]

Thanks for your response, but from what I can see I have defined and
assigned the value to the variable, before I compare it.

<xsl:variable name="isFailed" select="@type" />
.......
......

<xsl:when test="@type = 'END DATATABLE'">
<xsl:if test = "not('FAILED'=$ isFailed)">

Am I mis-understanding what you mean?

Cheers

Aidy

[Joseph Kesselman]

aidy wrote:

Thanks for your response, but from what I can see I have defined and
assigned the value to the variable, before I compare it.

You assigned it before, but deeper (within the conditional). That means
it goes out of scope before you can test it.
--
Joe Kesselman / Beware the fury of a patient man. -- John Dryden

[aidy]

Hi Joe

You assigned it before, but deeper (within the conditional). That means
it goes out of scope before you can test it.

Thanks. Now if I put this line above the template at global level

<xsl:variable name="isFailed" select="''" />
then within the template and conditional statement I can override it

<xsl:variable name="isFailed" select="@type" />
Will this overridden value be kept within the next conditional
statement (i.e. do we still have a global scope?)

<xsl:if test = "not('FAILED'=$ isFailed)">
I have tried to log a msg to find this out

<xsl:message>te st whether this appears</xsl:message>

in the command prompt I type

C:\ TESTLOG.xml SAFS.xsl test.htm

The test.htm is created, but I do not seem to recieve a mesage.

Cheers

Aidy

[Joseph Kesselman]

aidy wrote:

Will this overridden value be kept within the next conditional
statement (i.e. do we still have a global scope?)

No. XML variables are not mutable. When you try to override the value,
you're creating a new variable with its own scope.

--
Joe Kesselman / Beware the fury of a patient man. -- John Dryden

[aidy]

Joe,

I am really unsure on how to 'invert the problem'. This is a sample of
the XML

LOG_MESSAGE type="START DATATABLE" date="03-04-2006" time="16:46:18" >

<MESSAGE_TEXT>< ![CDATA[\\gbahes75\Proj ects\AddressSer vice\Datapool\C loseWindow.sdd]]></MESSAGE_TEXT>
</LOG_MESSAGE>
<LOG_MESSAGE type="WARNING" date="03-04-2006" time="16:46:30" >
<MESSAGE_TEXT>< ![CDATA[RobotJ Hook Not Installed or
Available.]]></MESSAGE_TEXT>
</LOG_MESSAGE>
<LOG_MESSAGE type="FAILED" date="03-04-2006" time="16:46:30" >
<MESSAGE_TEXT>< ![CDATA[WINDOW:ResultWi ndow could not be found on
screen. \\gbahes75\Proj ects\AddressSer vice\Datapool\C loseWindow.sdd at
Line 3]]></MESSAGE_TEXT>
<MESSAGE_DETAIL S><![CDATA["Type=Window;Ca ption={AddressS ervice Web
Client*}"]]></MESSAGE_DETAILS >
</LOG_MESSAGE>
<LOG_MESSAGE type="END DATATABLE" date="03-04-2006" time="16:46:30" >

What I want to do is that if there isn't an attribute type="FAILED"
between the attributes type="START DATATABLE" and type="END DATATABLE"
log a pass otherwise log a fail. I can't see any other way of doing
this except looping through the hierarchy. Could you please give me a
pseudo code example?

Aidy