Working with Both xsl:if and xsl:choose in XSLT

This is the third article in a series focusing on developing XSLT-oriented applications using ASP.NET 2.0. Even though the series is based on ASP.NET 2.0, I use it only as a transformation engine. The entire focus will be on working with XSLT. You can use any transformation engine according to your requirements (such as Java or others).

Contributed by
Rating: 5 stars5 stars5 stars5 stars5 stars / 12
December 18, 2006
Rate this Article:
MEH MEH++


SEARCH ASP FREE
TOOLS YOU CAN USE

advertisement

A downloadable zip file is available for this article.

In this article, I will focus on working with the "xsl:choose" and "xsl:if" constructs available in XSLT.  The entire setup and sample XML for this article is the same as that of the first two articles in this series.  If you come across any problems, I strongly suggest you to go through my first and second articles in this series.

The entire solution (source code) for this article is available as a free download (in the form of a zip).  All the applications in this series have been developed using Microsoft Visual Studio 2005 Professional Edition on Microsoft Windows Server 2003 Standard Edition together with Microsoft SQL Server 2005 Developer Edition as the database.  You can even directly copy and paste the code given in this article and save with the XML or XSL extensions and work with your own XSL parsers/engines.

I didn't really test any of the code in any of the tools/IDEs/servers/editions/versions.  If you have any problems, please feel free to post in the discussion area.

Working with "xsl:if" in XSLT

I already introduced "xsl:choose" in my previous article.  Now, I will start discussing "xsl:if."

Let us start with a business need. Say that I would like to have all the employee details listed with:

  • salary in red, if earnings are more than 4000
  • salary in blue, if earnings are more than 3000 and less than 4000

I would like to implement the above business need using the "xsl:if" construct in XSLT.  The following is the entire code for the same:

<?xml version="1.0" encoding="utf-8"?>

<xsl:stylesheet version="1.0"

    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:template match="/">

      <table border="1">

      <xsl:apply-templates select="SQLData/Rows" />

      </table>

</xsl:template>  

<xsl:template match="SQLData/Rows">

      <tr>

            <td>

                  <xsl:value-of select="Empno"/>

            </td>

            <td>

                  <xsl:value-of select="Ename"/>

            </td>

            <xsl:apply-templates select="Sal" />

            <td>

                  <xsl:value-of select="Deptno"/>

            </td>

      </tr>

</xsl:template>

<xsl:template match="Sal">

      <xsl:if test="text() &gt; '4000'">

            <td style="color: red">

                  <xsl:value-of select="."/>

            </td>

      </xsl:if>

      <xsl:if test="text() &gt; '3000' and text() &lt; '4000'">

            <td style="color: blue">

                  <xsl:value-of select="."/>

            </td>

      </xsl:if>

      <xsl:if test="text() &gt; '0' and text() &lt; '3000'">

            <td>

                  <xsl:value-of select="."/>

            </td>

      </xsl:if>

</xsl:template>

</xsl:stylesheet>

When the above code gets executed, you are likely to get the following transformation:

<table border="1">

      <tr>

            <td>1001</td>

            <td>Jag</td>

            <td style="color: red">4400</td>

            <td>10</td>

      </tr>

      <tr>

            <td>1002</td>

            <td>Chat</td>

            <td>2800</td>

            <td>20</td>

      </tr>

      <tr>

            <td>1003</td>

            <td>Winner</td>

            <td style="color: blue">3700</td>

            <td>10</td>

      </tr>

      <tr>

            <td>1004</td>

            <td>Dhan</td>

            <td style="color: red">5000</td>

            <td>20</td>

      </tr>

</table>

 

The most important problem with "xsl:if" is that it doesn't have (at the time of this writing) any "else" structure.  If you need an "else" structure, you may have to use "xsl:choose" as explained in my previous article.

Nesting xsl:if within another

In the previous section, I already introduced "xsl:if."  And now, I want to nest "xsl:if" within another and make things a bit complicated.  To do that, we may have to modify our business need. 

Let us modify our business need in such a way that I would like to have all the employee details listed with:

  • salary in red, if earnings are more than 4000
  • salary in blue, if earnings are more than 3000 and less than 4000
  • salary must not be shown for the employees working in department 10

The entire XSLT code for the above business need is as follows:

<?xml version="1.0" encoding="utf-8"?>

<xsl:stylesheet version="1.0"

    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:template match="/">

      <table border="1">

      <xsl:apply-templates select="SQLData/Rows" />

      </table>

</xsl:template>  

<xsl:template match="SQLData/Rows">

      <tr>

            <td>

                  <xsl:value-of select="Empno"/>

            </td>

            <td>

                  <xsl:value-of select="Ename"/>

            </td>

            <xsl:apply-templates select="Sal" />

            <td>

                  <xsl:value-of select="Deptno"/>

            </td>

      </tr>

</xsl:template>

<xsl:template match="Sal">

      <xsl:if test="./following::Deptno[1]/text() != '10'">

            <xsl:if test="text() &gt; '4000'">

                  <td style="color: red">

                        <xsl:value-of select="."/>

                  </td>

            </xsl:if>

            <xsl:if test="text() &gt; '3000' and text() &lt; '4000'">

                  <td style="color: blue">

                        <xsl:value-of select="."/>

                  </td>

            </xsl:if>

            <xsl:if test="text() &gt; '0' and text() &lt; '3000'">

                  <td>

                        <xsl:value-of select="."/>

                  </td>

            </xsl:if>

      </xsl:if>

      <xsl:if test="./following::Deptno[1]/text() = '10'">

            <td>

                  NA

            </td>

      </xsl:if>

</xsl:template>

</xsl:stylesheet>

When the above code gets executed, you are likely to get the following transformation:

<table border="1">

      <tr>

            <td>1001</td>

            <td>Jag</td>

            <td>

                  NA

            </td>

            <td>10</td>

      </tr>

      <tr>

            <td>1002</td>

            <td>Chat</td>

            <td>2800</td>

            <td>20</td>

      </tr>

      <tr>

            <td>1003</td>

            <td>Winner</td>

            <td>

                  NA

            </td>

            <td>10</td>

      </tr>

      <tr>

            <td>1004</td>

            <td>Dhan</td>

            <td style="color: red">5000</td>

            <td>20</td>

      </tr>

</table>

Within the above XSLT code, the most confusing issue will be the following:

xsl:if test="./following::Deptno[1]/text() != '10'">

That tests whether the next sibling node named "Deptno" does or does not equal 10. If you are new to this, I suggest you to refer my second article in this series.

Nesting xsl:choose within xsl:if

As you are familiar with both "xsl:if" and "xsl:choose" by now, let us nest them together.  If you are new to "xsl:choose," I suggest you go through my second article in this series.

Let us modify our business need in such a way that I would like to have all the employee details listed with:

  • salary in red, if earnings are more than 2500 and less than 4000
  • salary must not be shown for the employees working in department 10

The entire XSLT code for the above business need is as follows:

<?xml version="1.0" encoding="utf-8"?>

<xsl:stylesheet version="1.0"

    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:template match="/">

      <table border="1">

      <xsl:apply-templates select="SQLData/Rows" />

      </table>

</xsl:template>  

<xsl:template match="SQLData/Rows">

      <tr>

            <td>

                  <xsl:value-of select="Empno"/>

            </td>

            <td>

                  <xsl:value-of select="Ename"/>

            </td>

            <xsl:apply-templates select="Sal" />

            <td>

                  <xsl:value-of select="Deptno"/>

            </td>

      </tr>

</xsl:template>

<xsl:template match="Sal">

      <xsl:if test="./following::Deptno[1]/text() != '10'">

            <xsl:choose>

                  <xsl:when test="text() &gt; '2500' and text() &lt; '4000'">

                        <td style="color: red">

                              <xsl:value-of select="."/>

                        </td>

                  </xsl:when>

                  <xsl:otherwise>

                        <td>

                              <xsl:value-of select="."/>

                        </td>

                  </xsl:otherwise>

            </xsl:choose>

      </xsl:if>

      <xsl:if test="./following::Deptno[1]/text() = '10'">

            <td>

                  NA

            </td>

      </xsl:if>

</xsl:template>

</xsl:stylesheet>

When the above code gets executed, you are likely to get the following transformation:

 

<table border="1">

      <tr>

            <td>1001</td>

            <td>Jag</td>

            <td>

                  NA

            </td>

            <td>10</td>

      </tr>

      <tr>

            <td>1002</td>

            <td>Chat</td>

            <td style="color: red">2800</td>

            <td>20</td>

      </tr>

      <tr>

            <td>1003</td>

            <td>Winner</td>

            <td>

                  NA

            </td>

            <td>10</td>

      </tr>

      <tr>

            <td>1004</td>

            <td>Dhan</td>

            <td>5000</td>

            <td>20</td>

      </tr>

</table>

Nesting xsl:if within xsl:choose

Let us modify our business need in such a way that I would like to have all the employee details listed with:

  • salary in red, if earnings are more than 2500 and less than 4000
  • salary must not be shown for the employees working in department 10 whose salary would otherwise be shown in red.

The entire XSLT code for the above business need is as follows:

<?xml version="1.0" encoding="utf-8"?>

<xsl:stylesheet version="1.0"

    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:template match="/">

      <table border="1">

      <xsl:apply-templates select="SQLData/Rows" />

      </table>

</xsl:template>  

<xsl:template match="SQLData/Rows">

      <tr>

            <td>

                  <xsl:value-of select="Empno"/>

            </td>

            <td>

                  <xsl:value-of select="Ename"/>

            </td>

            <xsl:apply-templates select="Sal" />

            <td>

                  <xsl:value-of select="Deptno"/>

            </td>

      </tr>

</xsl:template>

<xsl:template match="Sal">

            <xsl:choose>

                  <xsl:when test="text() &gt; '2500' and text() &lt; '4000'">

                        <xsl:if test="./following::Deptno[1]/text() = '10'">

                              <td>

                                    NA

                              </td>

                        </xsl:if>

                        <xsl:if test="./following::Deptno[1]/text() != '10'">

                              <td style="color: red">

                                    <xsl:value-of select="."/>

                              </td>

                        </xsl:if>

                  </xsl:when>

                  <xsl:otherwise>

                        <td>

                              <xsl:value-of select="."/>

                        </td>

                  </xsl:otherwise>

            </xsl:choose>

</xsl:template>

</xsl:stylesheet>

When the above code gets executed, you are likely to get the following transformation:

 

<table border="1">

      <tr>

            <td>1001</td>

            <td>Jag</td>

            <td>4400</td>

            <td>10</td>

      </tr>

      <tr>

            <td>1002</td>

            <td>Chat</td>

            <td style="color: red">2800</td>

            <td>20</td>

      </tr>

      <tr>

            <td>1003</td>

            <td>Winner</td>

            <td>

                  NA

            </td>

            <td>10</td>

      </tr>

      <tr>

            <td>1004</td>

            <td>Dhan</td>

            <td>5000</td>

            <td>20</td>

      </tr>

</table>

Nesting xsl:choose within another

Up until now, we have seen several types of combinations using "xsl:if" and "xsl:choose."  Now, we shall embed "xsl:choose" within another "xsl:choose." 

In this case, I simply want to work with the same business need given in the previous section.  The entire modified XSLT code for the same business need is as follows:

<?xml version="1.0" encoding="utf-8"?>

<xsl:stylesheet version="1.0"

    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:template match="/">

      <table border="1">

      <xsl:apply-templates select="SQLData/Rows" />

      </table>

</xsl:template>  

<xsl:template match="SQLData/Rows">

      <tr>

            <td>

                  <xsl:value-of select="Empno"/>

            </td>

            <td>

                  <xsl:value-of select="Ename"/>

            </td>

            <xsl:apply-templates select="Sal" />

            <td>

                  <xsl:value-of select="Deptno"/>

            </td>

      </tr>

</xsl:template>

<xsl:template match="Sal">

            <xsl:choose>

                  <xsl:when test="text() &gt; '2500' and text() &lt; '4000'">

                        <xsl:choose>

                              <xsl:when test="./following::Deptno[1]/text() != '10'">

                                    <td style="color: red">

                                          <xsl:value-of select="."/>

                                    </td>

                              </xsl:when>

                              <xsl:otherwise>

                                    <td>

                                          NA

                                    </td>

                              </xsl:otherwise>

                        </xsl:choose>

                  </xsl:when>

                  <xsl:otherwise>

                        <td>

                              <xsl:value-of select="."/>

                        </td>

                  </xsl:otherwise>

            </xsl:choose>

</xsl:template>

</xsl:stylesheet>


You would receive the same output as discussed in previous section.

Other scenarios using xsl:if

In all of the previous examples, we worked with several conditions based on the data.  But "xsl:if" is not meant only for conditions.  It can also be used to test whether or not there exist any nodes/sub-nodes/leaves etc. under the current node.

For example, the following displays a message if the current "context" has any child elements named "dept no."

<xsl:if test="Deptno">

Got at least one Deptno as child element.

</xsl:if>

And not only that, you can also count the number of child elements using the following code fragment:

<xsl:if test="count(Deptno) = 1">

      Got only one Deptno as child element

</xsl:if>

Similarly, if you wanted to work with attribute values rather than text, you can provide attribute names preceded with "@".  The following code shows an example: 

<xsl:if test="@Sal < '2000')">

Salary is less than 2000 is "1667".

</xsl:if>

In all the above cases, I simply mentioned "xsl:if."  The same points apply to "xsl:choose."

I hope you enjoyed the article and any comments, suggestions, feedback, bugs, errors, enhancements etc. are highly appreciated at http://jagchat.spaces.live.com

blog comments powered by Disqus
ASP.NET ARTICLES

- Implementing ASP.NET 4.0 Page.MetaDescriptio...
- ASP.Net Development Tips
- Intro to Sessions in ASP.Net
- Google Maps API Introduction in ASP.NET usin...
- Creating an ASP.NET 3.5 Gridview Image Galle...
- Encrypt QueryString in ASP.NET 3.5 using VB....
- ASP.NET 3.5 Drop Down List Controls
- Connect to Access Database with ASP.Net
- Secure Audio Streaming with ASP.Net and Flash
- Dynamic Sitemap and Navigation in ASP.Net
- Implement Gzip and Deflate Compression in AS...
- Run ASP.Net in Ubuntu with Apache
- ASP.Net Mono Website Contact Forms
- ASP.Net URL Rewriting Methods
- Murach`s ASP.NET 4 Web Programming with C# 2...

ASP Web Hosting ASP.Net Web Hosting Windows Web Hosting
 
 
 

ASP Free Forums 
 RSS  Tutorials RSS
 RSS  Forums RSS
 RSS  All Feeds
Site Map 
Request Media Kit
Write For Us Get Paid 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
Privacy Policy 
Support 


© 2003-2012 by Developer Shed. All rights reserved. DS Cluster 5 - Follow our Sitemap
Most Popular Topics
All ASP.Net Tutorials