下面的类图说明SAML断言、安全数据解析器和控制对象之间的关系。
The following class diagram shows the relationship between the SAML assertion, security data parser, and control object.
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.
我们还传递了一个数据库连接到该解析器，以便它能够针对任何JD BC连接而工作。
We also pass a database connection to the resolver, so the resolver can work against any JDBC connection.
在您验证完一个类型数据库之后，您可以继续使用不同类型数据库的解析器来验证语句。
After you validate for one database type, you can proceed to validate statements with the parser for a different database type.
实际上，它主要用于测试和调试(在有机会完全配置解析器之前)，而非产品数据。
In practice, it is useful when you test and debug (before you've had a chance to configure the parser fully), but not for production data.
从理论上讲，解析器将报告数据直到发现第一个错误。
Theoretically, the parser could report data up to the first error it finds.
您可以使用定制解析器和数据转换器实现这一点。
例如，xml解析器可以从一个XML数据源提取数据。
For example, an XML parser extracts data from an XML data source.
例如，如果想同时处理日历数据和地址数据，就必须保证解析器同时支持这两种格式，或者使用两种不同的解析器。
For example, if you want to process both calendar data and address data, you have to make sure your parser supports both or use two different parsers.
将解析器包装在数据编出上下文内，这样就可以用最少的代码定义各种各样的访问方法。
Wrapping the parser within an unmarshalling context allows a wide variety of access methods to be defined with a minimum of code.
您应该创建一个类来包含表示解析器所得数据的对象实例。
You should create a class that contains an instance of the object that contains the data from the parser.
我质疑的第二个方面是使用SAX2解析器对文档进行数据分解。
The second aspect I questioned was the use of a SAX2 parser for unmarshalling documents.
解析器会将其输入视为文件的现有消息定义和数据的序列。
The parser will take as its input an existing message definition and the sequence of data in the file.
DB 2解析器只允许将有效的XML数据作为输入。
跟我们的前一场景一样，本例也依赖于解析器来执行数据库操作。
As in our previous scenarios, this example also relies on a resolver to execute the database operation.
最基本的解析器功能支持的数据类型不多，因此处理不规则或少见的数据(经常会遇到这种情况)成为最主要的困难。
The most basic parser functionality doesn't support a wide array of data types; therefore, irregular or unusual data, which is common, is a primary source of difficulty.
如果使用相同的用户标识创建数据库和运行解析器，该实例将运行得最好。
The example works best if the database is created and the parser run using the same userid.
相反，RXP就在解析器中建立数据结构。
In contrast, RXP builds the data structure right in the parser.
只不过这种方法不根据xml语法定义通用的数据模型，其解析器依赖应用程序程序员建立定制的数据模型。
Rather than define a generic data model based on the XML syntax, the parser relies on the application programmer to build a tailor-made data model.
您现在可以使用多个数据库解析器来验证脚本语法，然后依次在多个数据库连接中执行脚本。
You can now validate the syntax in scripts with multiple database parsers, and run scripts serially against multiple database connections.
另一方面，如果选择通过值绑定访问行数据，则必须咨询J SF变量解析器。
On the other hand, if you choose to access row data through the value binding, then you must consult the JSF variable resolver.
获取XML数据后，就可以在PHP xml解析器中处理这些数据了。
After you receive the XML data, you can process it in the PHP XML parser.
CDATA(字符数据)区域被解析器视为数据块，从而允许您在数据流中包含任意字符。
CDATA (character data) sections are treated as a block of data by the parser, allowing you to include any character in the data stream.
前面已经提到，解析器回调应用程序以建立数据模型，解析器处于控制地位。
The parser issues callbacks to the application to build the data model, as discussed before, but the parser is in control.
例如，不需要检查数据是否包含空字符，因为XML解析器绝不会传送一个空值。
For instance, you don't need to check whether the data contains null characters because an XML parser will never pass you a null.
要在不使用SDO 2.0的情况下完成相同的工作，开发人员需要理解xml解析器如何工作，并将数据解析逻辑与应用程序紧密集成。
To accomplish the same goal without using the SDO 2.0 would require the developer to understand how the XML parser works and tightly integrate the data parsing logic with the application.
每块XML数据可以附加到文件后；或提供给SAX解析器，该解析器作用于元素和内容并在处理完毕后废弃XML数据块。
Each block of XML could be appended to a file; or it could be fed to a SAX parser that ACTS on the elements and contents and discards it once processed.
现在已从请求返回所有数据，并将数据发送给了解析器，以便能获得更新提要中的博客条目标题。
You now have all the data returned from the request and send that data to the parser so that you can get the blog entry titles in the updates feed.
默认情况下，所选择的解析器是基于脚本所连接的数据库类型。
By default, the selected parser is based on the type of database that the script is connected to.
使用这种方法的缺点就是，因为原始数据放在了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).
应用推荐