处理用户错误和应用程序异常。
容器必须将应用程序异常传递到EJB客户端并且不改变该异常以及事务。
The container must pass application exceptions through to the EJB client without changing the exception nor changing the transaction.
我认为这是非常矛盾的，系统异常引发了自动回滚而应用程序异常不能。
I think this is rather inconsistent, that system exceptions cause automatic rollback while application exceptions specifically do not.
我们将创建一个症状数据库，该数据库描述这个应用程序异常以及改正该问题所需的步骤。
We will build a symptom database that describes this application exception and the steps required to remedy the problem.
反过来说，EJB 1.0下发生的应用程序异常在某种环境下会自动导致一个事务回滚。
Conversely, application exceptions under EJB 1.0 automatically caused a transaction rollback under certain circumstances.
因此，对于您的情况：您的应用程序异常类是RuntimeException的子类。
So, in your situation: your application exception classes are subclasses of RuntimeException.
但更重要的是，尽管拦截应用程序异常的技术广为人知，但它真的适合于Web服务调用吗？
But, more importantly, although the technique of intercepting application exceptions is well-known, is it really appropriate in case of Web services invocations?
当它自动执行回滚的同时，也将您有含义的描述的应用程序异常转换成了通用的异常。
While it performs the rollback automatically, it also converts your hopefully meaningful and descriptive application exception to a generic one.
与容器处理应用程序异常的方式有关的EJB规范的版本之间的差别可能会要求对设计的再次考虑。
Differences between versions in the EJB specification with respect to the way the container handles application exceptions may require reconsideration of the design.
在云计算环境中，编码集名称不相容会导致数据损坏、应用程序异常、系统崩溃、可移植性差和转换失败。
In a cloud computing environment, problems with code-set name compliance can cause data corruption, application exceptions, system crashing, poor portability, and conversion failures.
理论上，您可以让所有web层方法预期处理和响应单个应用程序异常，正如我们在先前的一些示例中所做的一样。
Theoretically, you could have all of your Web tier methods expect and respond to a single application exception, as we did in some of our previous examples.
您还经常需要给这些更具体的异常(这些异常也是主应用程序异常的子类)提供子类，以提供更具体的异常。
You will also often need to provide subclasses of these more specific exceptions (which are in turn subclasses of the main application exception), providing even more specific exceptions.
在我描述JAX - RPC异常处理时，我将更深入地看一下语义上的意思以及应用程序异常之间的关系(在WSDL的上下文环境里)。
I'll take a closer look at the semantic meaning and relation of these application exceptions (in the context of WSDL) when I describe JAX-RPC exception handling.
是的，我知道有些应用程序极少或从来不会抛出异常。
Right. I have witnessed some applications that in fact rarely or never throw exceptions.
通过分析跟踪文件，您可以检测异常的应用程序行为，比如数据库资源漏泄。
By analyzing the trace files, you can detect abnormal application behavior, such as database resource leaks.
企业应用程序在构建时通常都不会注意异常处理。
Enterprise applications are often built with almost no attention given to exception handling.
第四个参数表示被应用程序所抛出的异常的实例。
The fourth parameter represents the actual instance of the exception thrown by the application.
在现实的应用程序中，需要额外的异常处理来处理这类情况。
In a real-world application, additional exception handling would be needed to handle this sort of situation.
应用程序代码也往往捕获并转换异常，其间常常废弃许多详细信息。
Application code also tends to catch and translate exceptions, usually discarding many details in the process.
如果服务线程因编程错误而没有处理某个异常，则会造成整个应用程序崩溃。
If a service thread does not handle an exception due to programming error, it will kill the whole application.
这将导致您在第一次运行该应用程序时可能看到的异常消息。
This leads to the exception messages that you might have noticed when you ran the application for the first time.
在代码中处理SQL异常并运行应用程序，以此判断SQL是否有效。
Handle SQL exceptions in your code and run your applications to find out whether the SQL is valid or invalid.
对于BPM应用程序，业务和流程异常可能需要不同的处理机制。
For a BPM application, business and process exceptions may need different handling mechanisms.
异常处理应用程序块使用不恰当，这是常见的一个隐晦的无穷递归情形。
A bit of an obscure infinite recursion situtaion that unfortunately is pretty common is incorrect usage of the Exception Handling application block.
应该在整个应用程序中一致地处理异常。
You should handle exceptions coherently throughout the application.
当前流程、异常和应用程序。
当应用程序产生异常时，复杂性的增加会使得异常原因的分析难度加大。
When exceptions are generated in the application, additional complications can make it more difficult to analyse the exception's cause. Two examples of this dilemma are
本文中的实例是一个应用程序，该应用程序帮助一家银行的雇员识别行为异常的客户。
The running example in this article is an application that helps employees of a bank identify customers that show unusual behavior.
但是，真正的好处在于将这种技术作为出发点，以创建特定于应用程序的异常层次结构。
The real benefit, however, is in using this technique as the starting point to create an application-specific hierarchy of exceptions.
如果装载了该应用程序的系统异常繁忙，那么利用网格计算，应用程序可以在格网中空闲的或未充分利用的系统上运行。
With grid computing, if the system housing the application is unusually busy, the application may run on an idle or underutilized system that is part of the grid.
应用推荐