This helper function simplifies the addition of a node to the document, as shown in Listing 4.
此助手函数简化了将一个节点添加到文档中的步骤，如清单4所示。
The node would issue this call, as illustrated in the code sample in Listing 3.
这个节点将发布这个调用，如清单3中的代码样本所示。
Sometimes you only need to know if a node contains a string or not (see Listing 15).
有时只需要知道节点是否包含某个字符串(参见清单15)。
So I wrote a filter function that, given a node, determines whether it starts an XML island. Listing 2 shows the code.
于是我编写了一个过滤器函数，判断给定的节点是否启动了一个XML岛，清单2显示了该代码。
We can easily make a finder, too - let's make one that finds the first node of a certain type in Listing 18.
我们也可以轻松地创建一个查找器，让我们来创建一个查找器，查找清单18中某种类型的第一个节点。
When the script is running, it outputs the node name and server name where the migration is performing (Listing 5).
当脚本运行时，在迁移执行的地方输出节点名和服务器名（清单5）。
The XSLT script in Listing 3 replaces all character data with a node of the same length comprising only spaces.
清单3 中的XSLT脚本用长度相同但仅包含空格的节点代替所有字符数据。
Timeout handler (Listing 16) is invoked when a task node timer is fired.
任务节点计时器触发调用的超时处理器(清单16)。
The remove tree node style is defined as shown below in Listing 32.
删除树节点样式的定义如下面的清单32所示。
In Listing 24, a node is being converted into an attribute.
在清单24中，要将一个节点转换为属性。
The rename tree node style is defined as shown in Listing 34.
此重命名树节点样式的定义如清单34所示。
The change in the node configuration as a result of this job is shown in Listing 28.
此作业的结果所导致的节点配置的变化如清单28所示。
Another common action is to set the value of a node to a desired value, as shown in Listing 3.
另一项常用的操作是将节点的值设置为希望的值，如清单3所示。
Listing 2 shows how to obtain the meta data of a content node.
清单2显示了如何获取内容节点的元数据。
This helper function simplifies the addition of a node to the document, as shown in Listing 4.
这个助手函数简化了文档节点的添加，如清单4所示。
Listing 5 is equivalent to Listing 3, but the same local node IDs are used as in Listing 4.
清单5与清单3等价，但所用的本地节点标识与清单4中的相同。
You also need to specify the node name, shown in Listing 6.
您还需要指定节点名，如清单6所示。
Another common action is to set the value of a node to a desired value, as shown in Listing 3.
另一项常见操作是将节点值设置成期望的值，如清单3中所示。
If complete removal of the character data is too extreme and you want to preserve at least the length of each node, a variation on Listing 1 might be useful.
如果彻底删除字符数据过于极端，希望至少保留每个节点的长度，可以使用清单1的一个变体。
Listing 12 creates a node element and USES Figure 3 to compose the node's background.
清单12创建了一个节点元素，并使用图3作为背景图。
The package path of these element and attribute classes is dependent on the namespace of the XML node, whose naming is composed by use of the namespace, local name, and node type (see listing 2).
这些元素和属性类的包路径依赖于xml节点的名称空间，其名称由名称空间、本地名称和节点类型组成(见清单2)。
Listing 4 shows the output of the run on the node ha1.
清单4展示了在节点ha1上运行这个程序的输出。
Listing 5 shows the additions to the node EditPart implementation for model notification.
清单5显示了向节点EditPart实现添加的模型通知内容。
Modify the Xdmx start command to include the third node, as in Listing 5.
然后修改Xdmx的启动命令，包含第三个节点，如清单5所示。
This is an XMLList object, that is it is a list where each element corresponds to a photo node from the XML seen in Listing 1.
这是一个XMLList对象，即一个列表，其中的每个元素都对应于来自清单1所示的XML的一个photo节点。
The DocumentRoot instance object is the first retrieved, and is the root node used in the operation logic in Listing 8.
所检索到的第一个对象是DocumentRoot实例对象，此对象在清单8中的操作逻辑中作为根节点使用。
A snippet of the rename node handler is shown in Listing 33.
rename节点处理程序的代码片段如清单33所示。
Listing 2 shows a custom tree node.
清单2显示了一个定制的树节点。
This contains a loop in ESQL which builds a request message for each e-mail address and propagates this request message to the plug-in node (see Listing 2).
在ESQL中包含了一个循环，该循环为每个e-mail地址创建一个请求消息并且把该请求信息广播到插件节点（参见清单2）。
This contains a loop in ESQL which builds a request message for each e-mail address and propagates this request message to the plug-in node (see Listing 2).
在ESQL中包含了一个循环，该循环为每个e-mail地址创建一个请求消息并且把该请求信息广播到插件节点（参见清单2）。
应用推荐