多线程进程中的异常处理。
SOA中的异常处理非常依赖服务异常定义语义。
Exception processing in SOA relies heavily on Service exception definitions semantics.
表7展示了solidDBRETURN SQLERROROF cursorname 语句的使用，与DB2 中的异常处理形成对比。
Table 7 shows the use of the solidDB RETURN SQLERROR OF cursorname statement compared to exception handling on DB2.
这个过程中也可能有例外情况出现，例如处理无效订单、解决系统异常，以及其它的问题。
There might be exceptions to this normal processing such as the handling of invalid orders, dealing with system exceptions, and other issues.
对于这些情形，可添加一条异常规则，将部件指示器处理为令牌中的子字符串。
For such cases, an exception rule can be added for processing part indicators as substrings in tokens.
以下的复杂问题在单片应用程序中并不是什么大问题，为了支持SOA下的异常处理，必须被处理[2]。
The following complex issues which are not a major concern in monolithic applications have to be dealt to support exception processing in SOA [2].
在现实的应用程序中，需要额外的异常处理来处理这类情况。
In a real-world application, additional exception handling would be needed to handle this sort of situation.
本文还包括有关JMS 1.1中的统一域类、异常处理、传输绑定和其他最佳实践等信息。
Also included with this article are additional sections on the unified domain classes in JMS 1.1, exception handling, transport bindings, and other best practices.
当在触发器的处理过程中抛出异常时，触发器终止，导致触发器触发的整个语句回退。
When an exception is thrown during processing of a trigger, the trigger aborts, and the entire statement that caused the trigger to fire is rolled back.
例如，管理员可能处理任务中的异常(例如，无效的命令、系统崩溃)。
For example, an administrative staff could handle an exception in a task (for example, invalid order, system failure).
假定对应用程序中的所有类有统一的异常处理。
Let's say that you wanted consistent exception handling for all of the classes in your application.
BusinessProcessModelingNotation (BPMD)支持一些异常处理构造，它们可用于对业务流程中的异常流进行建模。
Business process Modeling Notation (BPMD) supports exception handling constructs that you can use to model exceptional flows within the business process.
处理多线程程序中的异常。
我们同样为附加对象（例如在异常处理中，作为输入的 ExceptionInput）以及工具对象（例如用于登录的 LogUtil）建模。
We also modeled additional objects, such as ExceptionInput to be used as input in exception handling, and utility objects like LogUtil for logging.
首先，一个catch块中可以处理多个指定类型的异常。
First, multiple exception types can be named as being handled by a single catch block.
图1展示了WebSphereLombardi中的一个典型异常处理场景。
A typical exception handling scenario in WebSphere Lombardi is depicted in Figure 1.
您还可以使用JUnit这样的单元测试框架中可用的构件来处理预期的异常。
You can also handle expected exceptions using the constructs available to you in unit testing frameworks such as JUnit.
与其他许多测试框架相反，可以把Google测试框架内置的断言部署在禁用了异常处理(通常由于性能原因)的软件中。
Contrary to a lot of other testing frameworks, Google's test framework has built-in assertions that are deployable in software where exception handling is disabled (typically for performance reasons).
您可为块定义模板，这样代码中即可包含您的企业中要用到的任何定制特性，例如定制的异常处理。
You can define the templates for the blocks, so the code can include any customized features you use in your enterprise — like custom exception handling.
在本系列的下一篇技巧文章中，我们将研究验证的另一方面：异常处理。
In the next tip in this series, we'll examine the other side of validation: exception handling.
在 C++中，无论何时在处理程序内捕获一个异常，关于该异常来源的信息都是不为人知的。
In C++, whenever an exception is caught within a handler, the information about the source of the exception is lost.
在架构良好的流程中，异常不应导致流程本身失败；相反，工作流应该遵循一条专门用于处理异常的途径(异常途径)。
In a well architected process, exceptions should not cause a process to fail; instead, the work flow travels down a path specifically designed to deal with that exception (the exception path).
如果您调用一个可能抛出检查异常的已有函数，您应编写一个包装器函数，捕获并处理此类异常，然后在XSLT中调用包装器方法。
If you invoke a preexisting function that can throw a checked exception, you should write a wrapper function that catches and handles that exception; then, invoke the wrapper method from XSLT instead.
客户中一个专门的错误处理程序接收这种异常，并且必须在解析器错误消息中检索出需要的信息！
A special error handler in the client receives this exception and must parse the parser's error message to retrieve the required information!
首先，在本实例中，用户需要在选择的BPEL活动中添加故障处理程序，来捕捉其抛出的异常。
First, in this example, you need to add a fault handler on the selected BPEL activity to catch the exceptions it throws.
注意，SQLPL中适当的异常处理要求每个过程有一个错误处理程序，这个错误处理程序应该可以很容易地告诉我们出错的过程。
Note that proper exception handling in SQL PL dictates that each procedure has an error handler that could easily enough have told us the failing procedure.
注释：必要的异常处理逻辑已经排除在这篇文章中的大多数样例代码，这主要是为了代码更清晰。
Note: The necessary exception handling logic has been excluded for clarity in most of the code examples in this article.
在业务整合过程中，异常处理和选取适当的路由与处理正常情况一样重要。
In business process integration, handling exceptions and taking the appropriate route is as important as handling normal cases (such as happy flow).
在本系列先前的技巧文章中，异常处理不属于讨论的核心范围之内。
In previous tips in this series, exception handling has been peripheral to our core discussion.
所有运行时异常都得到处理，要么在单独的活动中处理，要么在流程级别处理，具体取决于异常类型(无论流程是否需要重试)。
All the runtime exceptions are handled in either the individual activity, or in the process level depending on the type of the exception (whether it needs a retry or not).
应用推荐