使用类似与SAX2的接口(com . icl . saxon . Emitter)来显示这个节点流：它在如何表示名称和名称空间等细节方面与sax 2略有不同。
This stream of nodes is presented using a SAX2-like interface (com.icl.saxon.Emitter) : it differs from SAX2 in the details of how names and namespaces are represented.
为了获得有效的处理完整性，最好不要在消息流节点中产生其他线程。
For effective processing integrity it is not good to spawn additional threads in the message flow nodes.
这通常会导致一些额外工作，这是因为在移除节点后消息流就发生了更改，因此必须重新测试。
This often caused additional work as once the nodes were removed the message flow had changed and so had to be retested.
本部分讨论了在实现使用JMS传输节点的消息流时的性能因素。
This section discusses performance considerations when implementing message flows that use the JMS transport nodes.
正如已经描述过的，WSDL在配置使用SOAP节点的消息流方面起作重要作用。
As described already, WSDL plays the central role in configuring a message flow that USES the SOAP nodes.
消息流的节点之间设置了断点，用于调试。
Breakpoints are set between nodes in the message flows for debugging.
对于可以连接到计时器节点启动的消息流中的节点并没有任何限制。
There are no restrictions on the nodes that can be wired into a message flow that is initiated by a timer node.
本文还描述了许多演示如何在消息流中使用节点的使用模式。
The article also described a number of usage patterns that showed how to use the nodes within a message flow.
完成此步骤以后，WSRR节点将在消息流中变得可操作。
After this step is complete, the WSRR nodes will become operational within the message flow.
通过这种方式，您可以同时运行多个消息流(包括JMS传输节点)，其中每个消息流订阅或发布到不同的主题。
In this way, you can concurrently run multiple message flows (containing JMS transport nodes) where each message flow subscribes or publishes to a different topic.
动态视图跟踪经过物理配置节点的消息流。
The dynamic view traces the message flows through the nodes of the physical configuration.
它们以与现有节点相同的方式连接到消息流。
They are wired into a message flow in the same way that existing nodes are.
尽可能减少消息流中的节点数量。
Wherever possible reduce the number of nodes in the message flows.
这些节点被置于消息流的中部，接收到达已建立的连接的数据。
These nodes are placed in the middle of a message flow and receive data that arrives on connections that have already been established.
计时器节点与外部流启动方法的比较。
这个仲裁流的Callout节点必须配置为对模块化错误进行重试。
The Callout node of this mediation flow must be configured with retry on modeled faults.
当代理不可操作，或Timeout Notification节点对应的消息流已停止时，会发生何种情况？
What happens when the broker is not operational or the message flow with the TimeoutNotification node was stopped?
此工作区提供了消息流节点和UpdateManagerSite项目的所有源文件。
This workspace provides all the source files for the message flow nodes and Update Manager Site projects.
经过改进的测试工具，允许您使用MQInput或者HTTPInput节点测试消息流。
Improved test facility that lets you test message flows that start with an MQInput or HTTPInput node.
在进行消息流开发时，查找处理节点。
将需要在部署了包含Timeout Notification节点的消息流后立即发送此消息。
It will need to be sent immediately after the message flow containing the TimeoutNotification node is deployed.
重新提交由第一个仲裁流的Callout节点触发。
Resubmission is triggered by a Callout node in the first mediation flow.
包含TCPIPClient Input节点的消息流将侦听端口，等待服务器应用程序的连接尝试。
A message flow that contains a TCPIPClient Input node listens on a port, waiting for a server application to try to connect.
包含TCPIPServer Input节点的消息流将侦听端口，等待客户端应用程序的连接尝试。
A message flow that contains a TCPIPServer Input node listens on a port, waiting for a client application to try to connect.
启动代理，并部署使用前述配置的FileInput节点的消息流。
Start the broker and deploy a message flow which USES a FileInput node configured as previously specified.
这意味着可以将已编译的消息流文件与某些节点和配置节点的消息流参数分离。
This means that the compiled message flow file can be separated from some of the node and message flow parameters that configure it.
使用这种方法开发的节点，可以指定终端的数目和名称、该节点的属性，以及该节点是否作为流的输入节点。
Nodes developed using this method can specify the number and names of terminals and properties for the node, along with whether the node ACTS as an input node for a flow.
开始节点只能发出控制流，而停止和结束节点还可以接收数据流。
A start node can only issue control flow, while stop and end nodes can also receive data flow.
要开始开发映射，请将映射节点放置在消息流中。
To start to develop a mapping, place a mapping node in the message flow.
图6展示了居中节点所实现的双向工作流。
Figure 6 depicts bidirectional workflow implemented by the middle node.
应用推荐