Not equals to operator not working for when condition in xslt

[Geet mini]

Hi,

I'm writing below each condition  in my different xslt's based on requirement but not equals to operator is not working as expected. Can someone help me where am I doing wrong ?

<xsl:choose>       <xsl:when test="$storeid='1' and $storeid='2' and ($Type!= 'B1' or $Type!= 'B8') and ($Status='B11' or  $Status='B21')">            <xsl:copy-of select="."/>         </xsl:when>         <xsl:otherwise>            Do Nothing         </xsl:otherwise>      </xsl:choose>


<xsl:choose>       <xsl:when test="$storeid='1' and $storeid='2' and ($Type!= 'B1'  or $Status='B11' or  $Status='B21')">            <xsl:copy-of select="."/>         </xsl:when>         <xsl:otherwise>            Do Nothing         </xsl:otherwise>      </xsl:choose>

[g tsuji]

You're testing for the impossible. It is always false.
    $storeid='1' and $storeid='2' and ...
Whether you've in mind this, I cannot be sure.
    ($storeid='1' or $storeid='2') and ...

[Purvi Barot]

You haven't shown us what's in the variables.Rather surprisingly perhaps,

$storeid='1' and $storeid='2'

can be true, for example when the value of $storeid is the sequence (1, 2). But it would be a little odd to name the variable storeid if it can hold a sequence of integers. So I suspect that's not what you intended.

The expression

$Type!= 'B1' or $Type!= 'B8'

seems even less plausible. If $Type is an empty sequence, then the result will be false (because ()!='B1' is false, and ()!='B1' is also false). In all other cases the expression will be true:

[Paul Clapham]

Good point... if $Type is a node set then, well, the way that the = and != operators work on XSLT node set is maybe not how you think it works.

One node set is = another node set if there's any node in the first set which is equal to some node in the second set. And one node set is != another node set if there's any node in the first set which is not equal to some node in the second set. So, in particular != is not the negation of = when applied to node sets.

So you might want to check whether those variables are single values or whether they are node sets.

[g tsuji]

Yes, I would only supplement that by mentioning that sequence is a type introduced in xslt 2. One would need an xslt2 compliant processor to process the transformation.