Using TXMLDocument

The starting point for working with an XML document is the Xml.XMLDoc.TXMLDocument component.

The following steps describe how to use TXMLDocument to work directly with an XML document:

  1. Add a TXMLDocument component to your form or data module. TXMLDocument appears on the Internet category of the Tool Palette.
  2. Set the DOMVendor property to specify the DOM implementation you want the component to use for parsing and editing an XML document.
    The Object Inspector lists all the currently registered DOM vendors.
    For information on DOM implementations, see Using the Document Object Model.
  3. Depending on your implementation, you may want to set the ParseOptions property to configure how the underlying DOM implementation parses the XML document.
  4. If you are working with an existing XML document, specify the document:
    • If the XML document is stored in a file, set the FileName property to the name of that file.
    • You can specify the XML document as a string instead by using the XML property.
  5. Set the Active property to True.

Once you have an active TXMLDocument object, you can traverse the hierarchy of its nodes, reading or setting their values.

The root node of this hierarchy is available as the DocumentElement property.

For information on working with the nodes of the XML document, see Working with XML Nodes.

Working with XML Nodes

Once an XML document has been parsed by a DOM implementation, the data it represents is available as a hierarchy of nodes.

Each node corresponds to a tagged element in the document.

For example, given the following XML:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<!DOCTYPE StockHoldings SYSTEM "sth.dtd">
<StockHoldings>

<Stock exchange="NASDAQ">
<name>Borland</name>
<price>15.375</price>
<symbol>BORL</symbol>
<shares>100</shares>
</Stock>

<Stock exchange="NYSE">
<name>Pfizer</name>
<price>42.75</price>
<symbol>PFE</symbol>
<shares type="preferred">25</shares>
</Stock>

</StockHoldings>

TXMLDocument would generate a hierarchy of nodes as follows:

The root of the hierarchy would be the StockHoldings node.

StockHoldings would have two child nodes, which correspond to the two Stock tags.

Each of these two child nodes would have four child nodes of its own (namepricesymbol, and shares).

Those four child nodes would act as leaf nodes.

The text they contain would appear as the value of each of the leaf nodes.

Note:

This division into nodes differs slightly from the way a DOM implementation generates nodes for an XML document.

In particular, a DOM parser treats all tagged elements as internal nodes.

Additional nodes (of type text node) are created for the values of the namepricesymbol, and shares nodes.

These text nodes then appear as the children of the namepricesymbol, and shares nodes.

Each node is accessed through an Xml.XMLIntf.IXMLNode interface, starting with the root node, which is the value of the XML document component's DocumentElementproperty.

Working with a node's value

Given an IXMLNode interface, you can check whether it represents an internal node or a leaf node by checking the IsTextElement property.

  • If it represents a leaf node, you can read or set its value using the Text property.
  • If it represents an internal node, you can access its child nodes using the ChildNodes property.
BorlandStock := XMLDocument1.DocumentElement.ChildNodes[];
Price := BorlandStock.ChildNodes['price'].Text;

Working with a node's attributes

If the node includes any attributes, you can work with them using the Attributes property.

You can read or change an attribute value by specifying an existing attribute name.

You can add new attributes by specifying a new attribute name when you set the Attributes property:

BorlandStock := XMLDocument1.DocumentElement.ChildNodes[];
BorlandStock.ChildNodes['shares'].Attributes['type'] := 'common';

Adding and deleting child nodes

You can add child nodes using the AddChild method.

AddChild creates new nodes that correspond to tagged elements in the XML document.

Such nodes are called element nodes.

To create a new element node, specify the name that appears in the new tag and, optionally, the position where the new node should appear.

For example, the following code adds a new stock listing to the document above:

var
NewStock: IXMLNode;
ValueNode: IXMLNode;
begin
NewStock := XMLDocument1.DocumentElement.AddChild('stock');
NewStock.Attributes['exchange'] := 'NASDAQ';
ValueNode := NewStock.AddChild('name');
ValueNode.Text := 'Cisco Systems'
ValueNode := NewStock.AddChild('price');
ValueNode.Text := '62.375';
ValueNode := NewStock.AddChild('symbol');
ValueNode.Text := 'CSCO';
ValueNode := NewStock.AddChild('shares');
ValueNode.Text := '';
end;

You can delete child nodes using the methods of the ChildNodes property.

ChildNodes is an IXMLNodeList interface, which manages the children of a node.

You can use its Delete method to delete a single child node that is identified by position or by name.

For example, the following code deletes the last stock listed in the document above:

StockList := XMLDocument1.DocumentElement;
StockList.ChildNodes.Delete(StockList.ChildNodes.Count - );

Xml.XMLIntf.TNodeType

TNodeType = (
ntReserved,
ntElement,
ntAttribute,
ntText,
ntCData,
ntEntityRef,
ntEntity,
ntProcessingInstr,
ntComment,
ntDocument,
ntDocType,
ntDocFragment,
ntNotation);
Value Meaning

ntReserved

Not used

ntElement

The node represents an element.

Element nodes represent simple tags that have child nodes.

(Note that sometimes these child nodes do not appear when using IXMLNode.

For example child nodes of type ntText are typically hidden by IXMLNode and appear only as the value of the Text property).

The child nodes of an element node can have the following node types:

ntElement, ntText, ntCData, ntEntityRef, ntProcessingInstr, and ntComment.

Element nodes can also have attributes (ntAttribute).

Element nodes can be the child of a node of type

ntDocument, ntDocFragment, ntEntityRef, and ntElement.

ntElement -> ntElement -> ntElement ... --> ntText

ntAttribute

The node represents an attribute of an element.

It is not the child of another node, but its value can be accessed using the Attribute property of the element node's IXMLNode interface.

An attribute node can have child nodes of type ntText and ntEntityRef.

ntText

The node represents the text content of a tag.

A text node cannot have any child nodes,

but can appear as the child node of a node of type

ntAttribute, ntDocFragment, ntElement, or ntEntityRef.

ntCData

The node represents a CDATA section in the XML source.

CDATA sections identify blocks of text that would otherwise be interpreted as markup.

An ntCData node can't have any child nodes.

They can appear as the child of an ntDocFragment, ntEntityRef, or ntElement node.

ntEntityRef

The node represents a reference to an entity in the XML document.

This can be any type of entity, including character entity references.

The children of an entity reference node can be of the following types:

ntElement, ntProcessingInstr, ntComment, ntText, ntCData, and ntEntityRef.

The entity reference node can appear as the child of an

ntAttribute, ntDocFragment, ntElement, or ntEntityRef node.

ntEntity

The node represents an expanded entity.

Entity nodes can have child nodes that represent the expanded entity (for example, ntText and ntEntityRef nodes).

Entity nodes only appear as the child of an ntDocType node.

ntProcessingInstr

The node represents a processing instruction (PI) from the XML document.

A PI node cannot have any child nodes,

but can appear as the child node of a node of type

ntDocument, ntDocFragment, ntElement, or ntEntityRef.

ntComment

The node represents a comment in the XML document.

Comment nodes do not have child nodes.

They appear as the child of an

ntDocument, ntDocFragment, ntElement, or ntEntityRef node.

ntDocument

The node represents a document object, which is the root of the entire XML document.

Document nodes have a single ntElement node as a child (the DocumentElement).

In addition, they can have child nodes of type

ntProcessingInstr, ntComment, and ntDocType.

Because the document is the root of the XML document, it never appears as a child node.

ntDocType

The node represents the document type declaration, indicated by the <!DOCTYPE > tag.

The document type node can child nodes of type

ntNotation and ntEntity.

It always appears as the child of the document node.

ntDocFragment

The node represents a document fragment.

A document fragment node associates a node or subtree with a document without actually being contained in the document.

Document fragment nodes can have child nodes of type

ntElement, ntProcessingInstr, ntComment, ntText, ntCData, and ntEntityRef.

It never appears as the child of another node.

ntNotation

A node represents a notation in the document type declaration.

It always appears as the child of an ntDocType node and

never has any child nodes.

Using TXMLDocument, Working with XML Nodes的更多相关文章

  1. Select XML Nodes by Name [C#]

    原文 http://www.csharp-examples.net/xml-nodes-by-name/ To find nodes in an XML file you can use XPath ...

  2. 转载---SQL Server XML基础学习之<6>--XQuery的 value() 方法、 exist() 方法 和 nodes() 方法

    /*------------------------------------------------------------------------------+ #| = : = : = : = : ...

  3. xml类型使用注意事项

    xml 的数据类型在平常的开发也是很常用的,燃鹅.也是有一些地方需要留意.今天我就分享几个测试的例子. 使用 xquery.exist (有但不仅仅限于)的注意事项.通常使用来判断节点是否存在,值是否 ...

  4. LINQ系列:LINQ to XML查询

    1. 读取XML文件 XDocument和XElement类都提供了导入XML文件的Load()方法,可以读取XML文件的内容,并转换为XDocument或XElement类的实例. 示例XML文件: ...

  5. XQuery的 value() 方法、 exist() 方法 和 nodes() 方法

    Xml数据类型 /*------------------------------------------------------------------------------+ #| = : = : ...

  6. 【译】用jQuery 处理XML-- jQuery与XML

    用jQuery 处理XML--写在前面的话 用jQuery 处理XML-- DOM(文本对象模型)简介 用jQuery 处理XML--浏览器中的XML与JavaScript 用jQuery 处理XML ...

  7. 在SQL2008中使用XML应对不确定结构的参数

    目的:统一接口,当数据结构发生变化时,前后端业务接口不发生变化,由业务具体解析结构. 规则:确定的接口用参数表(多行提交),不确定的参数用XML   DECLARE @r TABLE     (    ...

  8. 【转】Sql Server参数化查询之where in和like实现之xml和DataTable传参

    转载至: http://www.cnblogs.com/lzrabbit/archive/2012/04/29/2475427.html 在上一篇Sql Server参数化查询之where in和li ...

  9. SQL操作XML

    前面一段时间为了赶项目的进度,一直在加班,现在空闲了下来将前面碰到的问题整理了一下,发现了一些十分有用的,在此记录下来,看能不能帮助到遇到同样问题的朋友,此文仅是自己个人的意见,若存在问题,还望不宁赐 ...

随机推荐

  1. SPOJ DQUERY D-query (在线主席树/ 离线树状数组)

    版权声明:本文为博主原创文章,未经博主允许不得转载. SPOJ DQUERY 题意: 给出一串数,询问[L,R]区间中有多少个不同的数 . 解法: 关键是查询到某个右端点时,使其左边出现过的数都记录在 ...

  2. linux系统定时任务设置

    .使用at命令设置一次性定时任务 2.使用crontab设置周期性定时任务 1)cd /home 目录下,使用vi test.py创建文件,内容如下: #!/usr/bin/python#coding ...

  3. linux系统查找具体进程

    ps -ef | grep '查找内容' eg:ps -ef | grep '测试USB设备穿透'

  4. Delphi 中的自动释放策略

    来自万一老师的博客:http://www.cnblogs.com/del/archive/2011/12/21/2295794.html ------------------------------- ...

  5. [Spring Data JPA问题]Executing an update/delete query; nested exception is javax.persistence.TransactionRequiredException

    JPQL如下: @Modifying(clearAutomatically = true) @Query("UPDATE SyncTestFromTKDO SET stuAns = '' w ...

  6. SimpleCV install and "You need the python image library to save by filehandle"

    2015年5月3日 22:15:43 在win7下安装了python.simplecv,试着运行simplecv官网第一个hello world程序结果报错,提示说%python%/lib/site- ...

  7. Eolinker——前置用例返回的reponse值进行传递

    如下补充均是Eolinker的文档中未说明的部分 示例:将login接口reponse中的mobile的值作为参数,传递给”重置密码”的请求体“code" 1.打开”前置用例“,先点击左上角 ...

  8. 【转】EventBus 3.0使用详解

    原文:https://www.jianshu.com/p/f9ae5691e1bb 01 前言 当我们进行项目开发的时候,往往是需要应用程序的各组件.组件与后台线程间进行通信,比如在子线程中进行请求数 ...

  9. 开源IDS系列--解决barnyard2 停止运行 libmysqlclient.so.16.0.0

    现象: barnyard2运行一段时间后,会自行停止,未在/var/log/barnyard2或/var/log/suricata中发现相关日志. 排查: 在/var/log/message中存在以下 ...

  10. LoadRunner 使用虚拟IP测试流程

    LoadRunner 使用虚拟IP测试流程 LoadRunner 使用IP欺骗的原因 . 当某个IP的访问过于频繁,或者访问量过大是,服务器会拒绝访问请求,这时候通过IP欺骗可以增加访问频率和访问量, ...