另外，您还可以利用更复杂的分隔技术，使用消息解析器确定输入文件的记录的结束。
Alternatively you can use a more complex delimiting technique which is to use a message parser to determine the end of a record from an input file.
对WebSphereMessageBroker最新版本中的消息解析器进行了许多改进，扩展了功能和改进了性能。
A number of improvements have been to the message parsers in WebSphere message Broker in this latest release to extend function and improve performance.
作为文件处理的增添部分，已对WebSphereMessageBroker提供的现有消息解析器进行了扩展，添加了所谓的流解析。
As part of the addition of file processing there has been an extension to the existing message parsers which are supplied with WebSphere message Broker to add what is referred to as stream parsing.
当将表示输入消息的位流转换为可由代理处理的内部形式时，将会调用解析器。
A parser is invoked when the bit stream that represents an input message is converted to the internal form that can be handled by the broker.
每个解析器适合于称为消息域的特定消息分类(例如固定长度的二进制、分隔文本，或者XML)。
Each parser is suited to a particular class of messages (such as fixed-length binary, delimited text, or XML) known as a message domain.
lexer实际上完成了指出它位于消息中的哪个地方的一些任务，但是解析器仍将所有内容放在一起。
The lexer actually does some of the work of figuring out where in a message it is, but the parser still ties everything together.
connectionDidFinishLoading方法是最重要的，因为它启动读取数据并挑出消息的XML解析器。
The connectionDidFinishLoading method is the most important because it starts the XML parser that reads through the data and picks out the messages.
客户中一个专门的错误处理程序接收这种异常，并且必须在解析器错误消息中检索出需要的信息！
A special error handler in the client receives this exception and must parse the parser's error message to retrieve the required information!
另外，如果内部编码虽然存在但却不是一个有效的IBM编码模式，解析器将会发出SQL 16168n错误消息。
In addition, if the internal encoding exists and it is not a valid IBM encoding schema, the parser will issue a SQL16168N error message.
如果没有某个已提供的域适合于特定的消息格式，您可以编写自己的编程或描述解析器，以供您自己的用户定义的域使用。
If a supplied domain is not suitable for a particular message format, you can write your own programmatic or descriptive parser for use by your own user-defined domain.
如果访问不了模式位置或外部DTD，解析器就会发出错误消息。
If the schema location or the external DTD cannot be accessed, the parser issues an error message.
不幸的是，在大部分的时间里，由于它对于性能方面的影响，解析器的消息验证函数不能被启用。
Unfortunately, a majority of the time, the parser's message validation functions are not enabled due to its impact on performance.
例如，mrm解析器可以根据模型执行消息的运行时验证。
For example, the MRM parser can perform runtime validation of messages against the model.
并且，这两种情况下的结果错误消息也都是由XML解析器生成的。
The resulting error messages are in both cases also generated by the XML parser.
还随之提供一个解析器以支持消息的解析和写入。
This comes with a parser to support the parsing and writing of messages.
描述方法——您将编写单个通用的模型驱动的解析器程序来解析所有格式，每种消息格式由各自的模型表示。
Descriptive approach — You write a single general-purpose model-driven parser program to parse all formats, with each message format represented by its own model.
如果xml解析器读到这个序列，就认为您的CDATA区域结束，当解析器遇到真正的区域结尾时，可能会发出一条解析错误消息。
If the XML parser reads this sequence, it's the end of your CDATA section and you might end up getting a parser error when it hits the real section end.
解析器会将其输入视为文件的现有消息定义和数据的序列。
The parser will take as its input an existing message definition and the sequence of data in the file.
编程方法——编写特定的解析器程序来解析每种消息格式。
Programmatic approach — a specific parser program is written to parse each message format.
域确定了在解析和序列化该消息时使用的解析器。
A domain determines the parser that is used when parsing and serializing the message.
它具有模型驱动的通用解析器，可解析二进制消息、文本消息和XML文档。
It has a general-purpose, model-driven parser that can parse binary messages, text messages, and XML documents.
解析器必须同时理解位流的物理格式及其逻辑结构才能创建逻辑消息树。
The parser must understand both the physical format of the bit stream and its logical structure in order to create the logical message tree.
使用这种方法的缺点就是，因为原始数据放在了SOAP消息中，为此xml解析器必须扫描这些数据，即使它从来不会被使用到(例如，在一个SOAP处理中间体，类似于一个路由器)。
The drawback to this solution is that, since the raw data is within the SOAP message, it must be scanned by any XML parser, even if it is never used (for example, in an intermediary, like a router).
如果消息集中的消息模型将由mrm解析器在运行时使用，您必须将它们部署到代理。
If the message models in the message set are to be used by the MRM parser at runtime, you must deploy them to the broker.
将位流转换为逻辑消息树（解析）以及将逻辑消息树转换回位流（序列化或编写）的代理组件称为解析器。
The component of the broker that converts a bit stream into a logical message tree (parsing), and a logical message tree back into a bit stream (serializing or writing), is called a parser.
在这种情况下需要一个解析器，该解析器可以根据这些内存转储生成有意义的日志消息。
A parser is required in such cases, which generates meaningful log messages out of those memory dumps.
不透明解析的元素必须在消息流的输入节点的解析器选项选项卡上命名。
The elements which are to be opaquely parsed must be named on the parser options TAB of the input node of the message flow.
当以XML形式构建消息时，可以使用xml解析器来抽取消息字段的内容，而不考虑内容的大小。
When the message is built as XML, an XML parser can be used to extract the content of message fields without regard to the size of the content.
只有解析器才需要理解消息的物理格式——逻辑消息树与消息位流的物理格式无关。
Only the parser needs to understand the physical format of the message -- the logical message tree is independent of the physical format of the message bit stream.
解析器能够应对多个位流格式，如SOAP 1.1或 SOAP 1.2，也可以将其包装为带附件的 SOAP 或MTOM 消息。
The parser is able to cope with multiple bitstream formats such as SOAP 1.1 or SOAP 1.2 which may also optionally be wrapped as a SOAP with attachments or MTOM message.
应用推荐