XML Reference Guide

Mar 14, 2003

␡

⎙ Print

< Back Page 17 of 278 Next >

At this point, we have a working, static version of a hierarchical tree structure. The text is displayed based on whether a particular nodte is open or closed, and the appropriate "plus" or "minus" icon is displayed based on whether the node is open or closed. What we don't have is a way to make sure that the page is displayed with the appropriate node open to start with. Several ways exist to accomplish this. We could, if we choose, add a handler to the event that signifies that the page is loaded, and create JavaScript that would read the URL, detect the appropriate node, and display it in the open state.

In this case, however, we are going to use this opportunity to look at the way in which we can use .Net to display hierarchical data on a page. In a later entry, we'll do this with XML, but before we get to that point, let's look at the basic process.

.Net was designed from the beginning to make it easier to create dynamic web sites. One way in which it accomplishes this task is to create "controls" to which you can bind a set of data. For example, you can easily create an HTML table of data from a database by "binding" the data to a DataGrid control. The control then inserts all of the appropriate HTML, and even gives you the opportunity to specify styles are the table was a whole and of alternate rows.

But we need even more control than that. After all, we are not creating a table. If we follow the HTML at the end of our last entry, in order to match the existing structure of the InformIT.com site, we will need to use lists instead. Fortunately, .Net provides a control that gives us complete power over what it outputs. It's called a Repeater.

Let's look at what we're actually going to do. We have a set of data, or rather two sets of data, that represent topics in the InformIT XML and Web Services Guide. One set represents the main topics, or "C heads", and the other represents the subtopics, or "D heads" that appear under them in the hierarchy. We can represent them in a database such as the one in figure 1:

Guide Entry table

Notice that we have a pair of columns, id and parent_id, that relate the rows. For example, entry 12 is the parent for entries 14, 15, and 16. So we know that those items need to be displayed as children of entry 12. We can use this data relation in displaying the page, even if it doesn't formally exist in the database.

To display these items on the page, we'll start with a basic Repeater:

<%@ Page Language="VB" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
            "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
   <base href="http://www.informit.com" />
</head>
<body>
   <asp:Repeater id="CHeadRepeater" runat="server">

      <HeaderTemplate>
        <h1>Other page content, such as the top of the page</h1>
      </HeaderTemplate>

      <ItemTemplate>
          
         <p><a href="/guides/content.asp?g=xml&seqNum=<%# DataBinder.Eval(Container.DataItem, "id") %>">

            <%# DataBinder.Eval(Container.DataItem, "guideEntryTitle") %>
         </a></p>

      </ItemTemplate>

      <FooterTemplate>
        (The bottom of the page.)

      </FooterTemplate>
   </asp:Repeater>

</body>
</html>

Notice that the Repeater control uses a prefix of asp:. You're probably tempted to think, "oh, I recognize that, that's an XML namespace alias." Well, not really, but it does serve much of the same purpose; it tells the server that this is not a simple HTML element to display, and but rather an element to process. The runat attribute tells the server it's the one that should process it, and not the client.

As you might suspect, the HeaderTemplate and FooterTemplate elements are processed before the first item, and after the last item, respectively. The ItemTemplate element gets processed for each item the Repeater encounters, and that's where it gets interesting.

When the server encounters content in the <%# %> notation, it knows that it is supposed to process the contents based on the current row. For example, in this case we are executing the DataBinder.Eval function to get the id and guideEntryTitle attributes of the object representing the current item. We can add any function we want into one of these evaluation blocks, as we'll see shortly.

Now let's populate the Repeater:

<%@ Page Language="VB" %>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.Data.Odbc" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
            "http://www.w3.org/TR/REC-html40/loose.dtd">

<script language="VB" runat="server">

    Sub Page_Load(Src As Object, E As EventArgs)
        
        Dim MyConnection As OdbcConnection
        Dim MyCommand As OdbcCommand
        Dim ConnectionString As String
        Dim ds As DataSet 

        ConnectionString = _
           "Driver={Microsoft Access Driver (*.mdb)};" & _
           "Dbq="&Server.MapPath("guideentries.mdb")&";"
        
        myConnection = new Odbc.OdbcConnection(ConnectionString)

        Dim CHeads As OdbcDataAdapter = _
                 New OdbcDataAdapter( _
                     "select * from GuideEntries where parent_id=0 order by listOrder", _
                     myConnection )
        ds = New DataSet()
        CHeads.Fill(ds, "cheads")

        CHeadRepeater.DataSource = ds.Tables("cheads")
        CHeadRepeater.DataBind()

        myConnection.Close()
    End Sub
</script>

<html>
<head>
   <base href="http://www.informit.com" />

</head>
<body>
   <asp:Repeater id="CHeadRepeater" runat="server">
      <HeaderTemplate>
...

First, note that the server executes the Page_Load subroutine on, as you might have guessed, loading the page. To that end, we can use this opportunity to create a set of data and bind it to the Repeater. In my case, I'm running my ASP.net pages in a hosted environment in which I can only access an Access database, and only directly, so my first step is to create an ODBC connection. (If you are using, say, SQL Server, you'll load the System.Data.SqlClient classes instead.) Once we've got the connection, we create a DataAdapter that uses the connection to select all of the main topics, and use it to create a table in the DataSet. (We can tell they are main topics because they have a parent_ID of 0.)

It's important to note that we didn't just "populate" the DataSet, as we might have done with a RecordSet. One of the advantages of using a DataSet is that it can hold more than one table of data. In this case, we've created one arbitrarily called cheads. In a few moments, will create a second one and related to the first.

In the meantime, we are using this table as the data source for the Repeater, which we can identify from the id attribute we gave it in the body of the page. Once we assign it a data source, we bind the data to it, which gives us a page like figure 2:

a simple repeater

Now we can go ahead and create the data relation so we can display the subtopics:

...
        Dim CHeads As OdbcDataAdapter = _
                 New OdbcDataAdapter( _
                     "select * from GuideEntries where parent_id=0 order by listOrder", _
                     myConnection )
        ds = New DataSet()
        CHeads.Fill(ds, "cheads")

        Dim DHeads As OdbcDataAdapter = _
                 New OdbcDataAdapter( _
                      "select * from GuideEntries where parent_id > 0 order by listOrder", _
                      myConnection )
        DHeads.Fill(ds, "dheads")

        ds.Relations.Add("topicRelation", _
                             ds.Tables("cheads").Columns("id"), _
                             ds.Tables("dheads").Columns("parent_id"))

        CHeadRepeater.DataSource = ds.Tables("cheads")
        CHeadRepeater.DataBind()

        myConnection.Close()
    End Sub
</script> 
...

Here we have a second data adapter that adds a second table of data, called "dheads", to the DataSet. We can then create the parent-child relationship, topicRelation, by relating to the parent_id column in the child table to the id column in the parent table.

It's important to note that this case, in which both sides of the relation represent the same table in the database, is actually a rarity. In most cases, you will use this capability to draw a relations between, say, a customer table and an order table, or even different types of data.

Now that we've got the relation, we can actually nest another Repeater within the first:

...
   <asp:Repeater id="CHeadRepeater" runat="server">
      <HeaderTemplate>
        <h1>Other page content, such as the top of the page</h1>

      </HeaderTemplate>

      <ItemTemplate>
          
         <p><a href="/guides/content.asp?g=xml&seqNum=<%# DataBinder.Eval(Container.DataItem, "id") %>">
            <%# DataBinder.Eval(Container.DataItem, "guideEntryTitle") %>

         </a></p>
         <asp:Repeater id="DHeadRepeater" runat="server" 
              datasource='<%# Container.DataItem.Row.GetChildRows("topicRelation") %>'>

              <HeaderTemplate>
                 <div style="border: 1px dashed black">
              </HeaderTemplate>

              <ItemTemplate>
                  <%# Container.DataItem("guideEntryTitle") %><br />
              </itemtemplate>

              <FooterTemplate>
                  </div>

              </FooterTemplate>

          </asp:Repeater>
      </ItemTemplate>

      <FooterTemplate>
        (The bottom of the page.)
      </FooterTemplate>

   </asp:Repeater>
...

Notice that the new Repeater is within the ItemTemplate of the first one. That means it will be executed once for each row of the original set of data. But what will it use for data? Well, notice the datasource attribute. Remember, when the server encounters that type of evaluation block, it knows it has to calculate the contents based on the current row. Because we have created a data relation, the server can pull all of the child rows for the current row. The results look something like figure 3:

embedding a Child

Now that we have the basic Repeaters working, we can insert the actual HTML we want to output:

<html>
<head>
   <base href="http://www.informit.com" />

   <script type="text/javascript">

      function toggle(plusminus){
         if (plusminus.src=="http://www.informit.com/display/common/images/icons/plus.gif"){
            plusminus.src="/display/common/images/icons/minus.gif";
         } else {
            plusminus.src="/display/common/images/icons/plus.gif";
         }

         base = plusminus.parentNode;

         allChildren = base.getElementsByTagName("ul")[0].getElementsByTagName("li");
         for (i = 0; i < allChildren.length; i++){
            el = allChildren[i];
            if (el.style.display!="block"){
               el.style.display="block";
            } else {
               el.style.display="none";
            }
         }
      }

   </script>
   <style type="text/css">
      ul { display: block;
           list-style-type: none; }
   </style>

</head>
<body>
   <asp:Repeater id="CHeadRepeater" runat="server">
      <HeaderTemplate>
        <h2>Other page content, such as the top of the page</h2>
        <ul>

      </HeaderTemplate>

      <ItemTemplate>
         <li class="chead">
           <img src="/display/common/images/icons/plus.gif" alt="Expand" onclick="toggle(this)" />
           <span class="cheadT">
              <a href="/guides/content.asp?g=xml&seqNum=<%# DataBinder.Eval(Container.DataItem, "id") %>">

               <%# DataBinder.Eval(Container.DataItem, "guideEntryTitle") %>
              </a>
           </span>
           <ul style="display: block;">
          
             <asp:Repeater id="DHeadRepeater" runat="server" 
                datasource='<%# Container.DataItem.Row.GetChildRows("topicRelation") %>'>

                <ItemTemplate>
                   <li class="dhead" style="display: block">
                      <img src="/display/common/images/icons/plus.gif" alt="Expand" onclick="toggle(this)" />
                      <a href="/guides/content.asp?g=xml&seqNum=<%# Container.DataItem("id") %>">
                        <%# Container.DataItem("guideEntryTitle") %>

                      </a>
                   </li>
                </itemtemplate>

             </asp:Repeater>

           </ul>

         </li>

      </ItemTemplate>

      <FooterTemplate>
        </ul>
        (The bottom of the page.)
      </FooterTemplate>

   </asp:Repeater>

</body>
</html>

Now the page is virtually identical to the one we created earlier. (There is a slight change to the toggle script based on the fact that we will be manipulating the li elements directly.) As before, the JavaScript gets executed by the browser, not the server. But it is the server that creates the HTML, including the links.

The result looks like figure 4:

adding the correct HTML

At this point, we are essentially right back where we started. We have a page that displays our information, and opens and closes the appropriate node when requested. But we still need to have the server display nodes in their proper state to start with. We'll start by determining which main topic should be open:

<%@ Page Language="VB" %>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.Data.Odbc" %>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
            "http://www.w3.org/TR/REC-html40/loose.dtd">

<script language="VB" runat="server">

    Dim openId as String
    Dim ds As DataSet 

    function getParentId(childId as String)

       Dim targetRows As Array
       targetRows = ds.Tables("dheads").select("id="&childId)
       if (targetRows.Length = 0)
          return 0
       else 
          Dim thisRow As DataRow = targetRows.GetValue(0)
          return thisRow("parent_id")
       end if

    end function

    Sub Page_Load(Src As Object, E As EventArgs)
        
        Dim MyConnection As OdbcConnection
        Dim MyCommand As OdbcCommand
        Dim ConnectionString As String

        ConnectionString = _
           "Driver={Microsoft Access Driver (*.mdb)};" & _
           "Dbq="&Server.MapPath("guideentries.mdb")&";"
        
        myConnection = new Odbc.OdbcConnection(ConnectionString)

        Dim CHeads As OdbcDataAdapter = _
                 New OdbcDataAdapter( _
                     "select * from GuideEntries where parent_id=0 order by listOrder", _
                     myConnection )
        ds = New DataSet()
        CHeads.Fill(ds, "cheads")

        Dim DHeads As OdbcDataAdapter = _
                 New OdbcDataAdapter( _
                      "select * from GuideEntries where parent_id > 0 order by listOrder", _
                      myConnection )
        DHeads.Fill(ds, "dheads")

        ds.Relations.Add("topicRelation", _
                             ds.Tables("cheads").Columns("id"), _
                             ds.Tables("dheads").Columns("parent_id"))

        Dim selectedId As String = Request.QueryString("seqNum")&" "
        if (selectedId = " ")
           selectedId = 0
           openId = 0
        else 
           Dim parentId As String = getParentId(selectedId)
           if (parentId = 0)
              openId = trim(selectedId)
           else
              openId = parentId
           end if
        end if

        CHeadRepeater.DataSource = ds.Tables("cheads")
        CHeadRepeater.DataBind()

        myConnection.Close()
    End Sub
</script> 
...

A couple of things to notice here. First, we have declared two global variables, which will be needed by other functions. One, the DataSet, we've moved from inside the Page_Load subroutine so that we can use it in the getParentId function, which accepts an id value, and uses it to to locate a specific row in the dheads table. If the record exists in that table, it returns the value of the parent_id column. If not, it is assumed to be a main topic, which has a parent_id of 0.

We can then use that function to determine which main node should be open. If the URL for the request contains a main topic ID, then of course that is the topic that should be open. If the URL contains the id of a sub topic, we'll want to use its parent. The actual openId variable is global so we can use it to set the style for each subtopic:

...
          return thisRow("parent_id")
       end if

    end function

    function itemStyle(thisId as String)

       Dim style As String

       if (thisId = openId or getParentId(thisId) = openId) 
          style = "style='display: block'"
       else 
          style = "style='display: none'"
       end if
       return  style

    end function

    Sub Page_Load(Src As Object, E As EventArgs)
        
...         
             <asp:Repeater id="DHeadRepeater" runat="server" 
                datasource='<%# Container.DataItem.Row.GetChildRows("topicRelation") %>'>

                <ItemTemplate>
                   <li class="dhead" <%# itemStyle(Container.DataItem("id")) %>>

                      <img src="/display/common/images/icons/plus.gif" alt="Expand" onclick="toggle(this)" />
                      <a href="/guides/content.asp?g=xml&seqNum=<%# Container.DataItem("id") %>">
                        <%# Container.DataItem("guideEntryTitle") %>
                      </a>
                   </li>

                </itemtemplate>
...

The itemStyle function simply compares the current id (or rather, its parent id) with the openId and provides the appropriate style, which we add to the element using the evaluation block.

If you now display the page without specifying a node to open, it should open with all nodes closed:

all nodes closed

If you then display the page with a selected node, as in:

http://farmernick.somee.com/guide4.aspx?seqNum=12

one node open

you can see that node 12, "DOM and Java", is open. But what about we want one of the subtopics? For example, topic 29 is a sub topic of "DOM Level 3". So the URL:

http://farmernick.somee.com/guide4.aspx?seqNum=29

gives us a page like:

sub node open

because the server first determines the parent node and opens that one. Now all that's left is to make sure that the open node gets the appropriate icon:

...
          return thisRow("parent_id")
       end if

    end function

    function getPlusMinus(thisId As String)
       if (thisId = openId)
         return "minus.gif"
       else
         return "plus.gif"
       end if
    end function

    function itemStyle(thisId as String)

       Dim style As String

...
      <ItemTemplate>
         <li class="chead">
           <img src="/display/common/images/icons/<%# getPlusMinus(Container.DataItem("id"))%>" alt="Expand" onclick="toggle(this)" />
           <span class="cheadT">

...

Subtopics will never be displayed as open to start with, so they always get the plus sign, but in this case the open main topic does get the minus sign.

So now we have a working tree navigational structure, which displays on the page with the appropriate node open, and enables users to open and close other nodes at will.

< Back Page 17 of 278 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address