55 lines
		
	
	
		
			6.1 KiB
		
	
	
	
		
			HTML
		
	
	
	
			
		
		
	
	
			55 lines
		
	
	
		
			6.1 KiB
		
	
	
	
		
			HTML
		
	
	
	
| <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Retrieving Element Content</title><meta name="generator" content="DocBook XSL Stylesheets V1.61.2"><link rel="home" href="index.html" title="Libxml Tutorial"><link rel="up" href="index.html" title="Libxml Tutorial"><link rel="previous" href="ar01s03.html" title="Parsing the file"><link rel="next" href="ar01s05.html" title="Using XPath to Retrieve Element Content"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Retrieving Element Content</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ar01s03.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ar01s05.html">Next</a></td></tr></table><hr></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="xmltutorialgettext"></a>Retrieving Element Content</h2></div></div><div></div></div><p><a class="indexterm" name="id2525439"></a>
 | ||
| Retrieving the content of an element involves traversing the document
 | ||
|     tree until you find what you are looking for. In this case, we are looking
 | ||
|     for an element called "keyword" contained within element called "story". The
 | ||
|     process to find the node we are interested in involves tediously walking the
 | ||
|     tree. We assume you already have an xmlDocPtr called <tt class="varname">doc</tt>
 | ||
|     and an xmlNodPtr called <tt class="varname">cur</tt>.</p><p>
 | ||
|       </p><pre class="programlisting">
 | ||
| 	<a name="getchildnode"></a><img src="images/callouts/1.png" alt="1" border="0">cur = cur->xmlChildrenNode;
 | ||
| 	<a name="huntstoryinfo"></a><img src="images/callouts/2.png" alt="2" border="0">while (cur != NULL) {
 | ||
| 		if ((!xmlStrcmp(cur->name, (const xmlChar *)"storyinfo"))){
 | ||
| 			parseStory (doc, cur);
 | ||
| 		}
 | ||
| 		 
 | ||
| 	cur = cur->next;
 | ||
| 	}
 | ||
|       </pre><p>
 | ||
| 
 | ||
|       </p><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><a href="#getchildnode"><img src="images/callouts/1.png" alt="1" border="0"></a> </td><td valign="top" align="left"><p>Get the first child node of <tt class="varname">cur</tt>. At this
 | ||
| 	    point, <tt class="varname">cur</tt> points at the document root, which is
 | ||
| 	    the element "story".</p></td></tr><tr><td width="5%" valign="top" align="left"><a href="#huntstoryinfo"><img src="images/callouts/2.png" alt="2" border="0"></a> </td><td valign="top" align="left"><p>This loop iterates through the elements that are children of
 | ||
| 	  "story", looking for one called "storyinfo". That
 | ||
| 	  is the element that will contain the "keywords" we are
 | ||
| 	    looking for. It uses the <span class="application">libxml</span> string
 | ||
| 	  comparison
 | ||
| 	    function, <tt class="function"><a href="https://gnome.pages.gitlab.gnome.org/libxml2/devhelp/libxml2-parser.html#XMLSTRCMP" target="_top">xmlStrcmp</a></tt>. If there is a match, it calls the function <tt class="function">parseStory</tt>.</p></td></tr></table></div><p>
 | ||
|     </p><p>
 | ||
|       </p><pre class="programlisting">
 | ||
| void
 | ||
| parseStory (xmlDocPtr doc, xmlNodePtr cur) {
 | ||
| 
 | ||
| 	xmlChar *key;
 | ||
| 	<a name="anothergetchild"></a><img src="images/callouts/1.png" alt="1" border="0"> cur = cur->xmlChildrenNode;
 | ||
| 	<a name="findkeyword"></a><img src="images/callouts/2.png" alt="2" border="0"> while (cur != NULL) {
 | ||
| 	    if ((!xmlStrcmp(cur->name, (const xmlChar *)"keyword"))) {
 | ||
| 	<a name="foundkeyword"></a><img src="images/callouts/3.png" alt="3" border="0">	    key = xmlNodeListGetString(doc, cur->xmlChildrenNode, 1);
 | ||
| 		    printf("keyword: %s\n", key);
 | ||
| 		    xmlFree(key);
 | ||
|  	    }
 | ||
| 	cur = cur->next;
 | ||
| 	}
 | ||
|     return;
 | ||
| }
 | ||
|       </pre><p>
 | ||
|       </p><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><a href="#anothergetchild"><img src="images/callouts/1.png" alt="1" border="0"></a> </td><td valign="top" align="left"><p>Again we get the first child node.</p></td></tr><tr><td width="5%" valign="top" align="left"><a href="#findkeyword"><img src="images/callouts/2.png" alt="2" border="0"></a> </td><td valign="top" align="left"><p>Like the loop above, we then iterate through the nodes, looking
 | ||
| 	  for one that matches the element we're interested in, in this case
 | ||
| 	  "keyword".</p></td></tr><tr><td width="5%" valign="top" align="left"><a href="#foundkeyword"><img src="images/callouts/3.png" alt="3" border="0"></a> </td><td valign="top" align="left"><p>When we find the "keyword" element, we need to print
 | ||
| 	    its contents. Remember that in <span class="acronym">XML</span>, the text
 | ||
| 	    contained within an element is a child node of that element, so we
 | ||
| 	    turn to <tt class="varname">cur->xmlChildrenNode</tt>. To retrieve it, we
 | ||
| 	    use the function <tt class="function"><a href="https://gnome.pages.gitlab.gnome.org/libxml2/devhelp/libxml2-tree.html#XMLNODELISTGETSTRING" target="_top">xmlNodeListGetString</a></tt>, which also takes the <tt class="varname">doc</tt> pointer as an argument. In this case, we just print it out.</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png"></td><th align="left">Note</th></tr><tr><td colspan="2" align="left" valign="top"><p>Because <tt class="function">xmlNodeListGetString</tt> allocates
 | ||
| 	      memory for the string it returns, you must use
 | ||
| 	      <tt class="function">xmlFree</tt> to free it.</p></td></tr></table></div></td></tr></table></div><p>
 | ||
|     </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ar01s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ar01s05.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Parsing the file </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Using XPath to Retrieve Element Content</td></tr></table></div></body></html>
 |