XSLT has no exception handling of any kind.
XSLT没有任何类型的异常处理。
The delete trigger needs no exception handling.
删除触发器不需要异常处理。
Two changes have been made to exception handling.
关于异常处理有两个变化。
Exception case on asynchronous exception handling.
关于异步异常处理的异常情况。
Also notice that no exception handling is required.
还应注意，这里不需要异常处理。
They've implemented more flexible exception handling.
实现了更灵活的异常处理。
The last feature this article explores is exception handling.
本文探究的最后一项功能是异常处理。
The exception handling takes as much time as the code itself.
异常处理与代码本身所用时间一样多。
We skipped over the exception handling, which is important stuff.
我们跳过了异常处理，这是很重要的一部分。
Do the services support both exception handling and fault recovery?
服务同时支持异常处理和故障恢复吗？
In addition to that, this example does not include exception handling.
此外，该示例不包括异常处理。
The first one is trivial, nearly featureless, and has no exception handling.
第一个服务器十分简单，几乎没有什么功能，也没有任何异常处理。
There needs to be more exception handling and more thought put into error paths.
异常处理应该更多，对错误发生的路径也应多加考虑。
Specifically, I'll cover logging, exception handling, and transaction demarcation.
更确切地说，我将讨论日志、异常处理和事务界定。
When modeling business processes, fault and exception handling require special care.
在建模业务流程时，需要特别注意错误和异常处理。
A typical exception handling scenario in WebSphere Lombardi is depicted in Figure 1.
图1展示了WebSphereLombardi中的一个典型异常处理场景。
Another change in exception handling is exception chaining-either implicit or explicit.
异常处理的另一个改变是异常链—隐式或显式。
Seam Catch, which provides developers with a unified and robust exception handling process
SeamCatch，向开发者提供了统一、健壮的异常处理流程。
Enterprise applications are often built with almost no attention given to exception handling.
企业应用程序在构建时通常都不会注意异常处理。
Note that exception handling and business logic have been simplified for the sake of brevity.
请注意，出于简便的原因，例外处理和业务逻辑已经做了简化处理。
The exception handling solution approach will be based on the following design considerations
异常处理解决方案途径基于以下几点设计考虑
In the next tip in this series, we'll examine the other side of validation: exception handling.
在本系列的下一篇技巧文章中，我们将研究验证的另一方面：异常处理。
See Resources for more detailed information about exceptions and exception handling techniques.
有关异常和异常处理技术的更多信息参阅参考资料。
It provides functionality to handle common tasks such as input validation and exception handling.
它提供处理普通任务的功能，比如输入验证和异常处理。
Let's say that you wanted consistent exception handling for all of the classes in your application.
假定对应用程序中的所有类有统一的异常处理。
However, the sections on exception handling and concurrency mechanisms are still valid as advanced topics.
然而，关于异常处理和并发机制的章节，作为高级主题仍然是有效的。
The final flow-control tag is <c:catch>, which allows for rudimentary exception handling within a JSP page.
最后一个流控制标记是 <c:catch> ，它允许在JSP 页面内进行初级的异常处理。
In a real-world application, additional exception handling would be needed to handle this sort of situation.
在现实的应用程序中，需要额外的异常处理来处理这类情况。
Another issue that can have a negative effect on service layer reusability is your exception handling strategy.
可能会对服务层可重用性产生负面影响的另一个问题是您的异常处理策略。
An elegant solution to exception handling in SOA is applying SOA principles to exception handling implementation.
对异常处理实现应用soa原则，是SOA中一种优雅的异常处理解决方案。
应用推荐