该接口有三个方法，这三个方法都用来接收警告和错误通知。
The interface has three methods, all of them intended to receive warning and error notifications.
它是一个简单的、包含三种方法的接口，可以实现和处理所有类型的错误。
It's a simple, three-method interface that you can implement and handle all types of errors.
假设已存在某资产正用于某业务服务，那些组件接口可用于发掘那些通过自上而下分析所不能发现的其他业务错误。
If there are existing asset (s) for a business service, those component interfaces could be used to discover additional business errors that are otherwise not identified in top down analysis.
这个接口有一些方法来报告错误和显示信息消息。
The interface has methods to report errors and display information messages.
在这种情况下，应该始终尽量利用使用错误的请求-响应操作设计接口。
In these cases you should always strive to design your interfaces using request-response operations that use faults.
大多数错误是由于没有命名被声明为私有的关联链接和接口操作的属性。
Most of the errors were due to unnamed properties of association links and interface operations being declared as private.
这可能是由于目标系统接口无法理解此消息或由于消息导致了目标系统接口内的处理错误而造成的。
This will occur because of the target System Interfaces inability to understand the message or because the message is causing a processing error within the target System Interface.
为您提供将用户接口和系统模型链接起来的能力，使您更容易地找到错误。
Gives you the ability to link the user interface and the system models, enabling you to find errors more easily.
用户接口和系统模型之间的关联考虑到更有效的检查，因此导致在开发周期中，更早地找到更多错误。
The links between the user interface and the system models allow for more efficient reviews, thus resulting in more errors found earlier in the development cycle.
这缩短了应用程序开发时间，减少了错误，并且使之有可能通过允许程序员在行业标准接口中编码而巩固程序员的技能。
This improves application development time, reduces errors, and makes it possible to consolidate skills by allowing programmers to code in an industry standard interface.
当涉及处理xml解析和处理错误，关键问题不只是一个特定的SAX接口，还需要理解是什么驱动XML处理。
When it comes to handling XML parsing and processing errors, the key is not really a particular SAX interface as much as it is understanding what drives XML processing.
接口可选择性地指定在服务调用期间出错时所引发的任何错误。
The interface can optionally specify any faults that the operation might throw because of an error condition during the service call.
下一步就是运行您的单元测试，修正语法错误(即，编写一个类，使它实现您的测试刚定义的接口)，并再次运行测试。
The next step is to run your unit tests, fix the syntax errors (that is, implement the class with the interfaces just defined by your test), and run the tests again.
将会生成清单2、3和4中所示的接口和错误类。
It gives you the generated interface and fault classes shown in Listings 2, 3, and 4.
和SAX一样，可以使用该接口自定义错误的处理。
Just as when you work with SAX, you can use this interface to customize how errors are handled.
接口定义了与错误的三个级别或严重性对应的三个方法
The interface defines three methods that correspond to three levels or gravity of errors
现在我们已经将模拟ServiceController接口添加到MockCustomer组件，这时您将看到一条错误，因为我们还没有实现所需的操作（图25）。
Now that we have added the mock Service Controller interface to the MockCustomer component, you will see an error because we have no implementation of the required operations (Figure 25).
这应该解决任何与ServiceRegistry接口实现关联的导入错误。
This should resolve any import errors associated with the Service Registry interface implementations.
要添加错误消息，需要在资源上创建一个记号(接口IMarker)。
To append an error message, you need to create a marker (interface IMarker) on a resource.
然后，沿着这个方向，我将在下一个技巧中分析Error Handler接口，并解释如何用SAX在XML处理中加入错误处理和报告能力。
Along those lines, then, I'll look at the ErrorHandler interface in the next tip, and explain how it can add error handling and reporting capabilities to your XML processing with SAX.
Messenger是一个接口，XM用它来向用户报告进度和错误。
Messenger is an interface that XM uses to report progress and errors to the user.
Oerrs：从接口传输的错误数据包量。
Oerrs: The amount of error packets transmitted from the interface.
Ierrs：该接口所报告的错误的总数。
Ierrs: the amount of errors reported back from the interface.
如果您在IntegrationDeveloper中导出的接口的名称的首字母为大写形式，则不会遇到这些错误。
If the name of the interface you exported in Integration Developer began with an uppercase letter, you won't see these errors.
Messenger是与抽象错误和信息消息的接口。
Messenger is an interface to abstract error and information messages.
Error Handler接口定义错误事件。
使用ErrorHandler接口处理错误
要更正这个错误，单击Define打开 DefineCustomMediation对话框，在第一个面板中，设置Choosean existinginterface选项，这样可以设置已创建的接口。
To correct this error, click Define to open the Define Custom Mediation dialog, In the first panel, set the option Choose an existing interface so you can set the interface we have made.
出现错误的原因在于，我试图在连贯接口setter方法被调用之前调用appointment实例上的toString()方法。
The error occurs because I'm trying to call the toString() method on the appointment instance before the rest of the fluent-interface setter methods are called.
它鼓励细微的[半]服务(上述Blob的多个“接口”)，这忽略了少数分布式计算的错误。
ItIt encourages minuscule [half] -services (the multiple "interfaces" of said blob) that disregard few of the fallacies of distributed computing.
应用推荐