处理用户错误和应用程序异常。
我认为这是非常矛盾的，系统异常引发了自动回滚而应用程序异常不能。
I think this is rather inconsistent, that system exceptions cause automatic rollback while application exceptions specifically do not.
容器必须将应用程序异常传递到EJB客户端并且不改变该异常以及事务。
The container must pass application exceptions through to the EJB client without changing the exception nor changing the transaction.
当它自动执行回滚的同时，也将您有含义的描述的应用程序异常转换成了通用的异常。
While it performs the rollback automatically, it also converts your hopefully meaningful and descriptive application exception to a generic one.
但是这会使许多机场的安检通道人满为患，因为运输安全管理局新颁布的搜身检查程序异常繁杂。
But that could clog security lines at many airports, given the TSA's new especially thorough pat-down procedures.
我们将创建一个症状数据库，该数据库描述这个应用程序异常以及改正该问题所需的步骤。
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?
与容器处理应用程序异常的方式有关的EJB规范的版本之间的差别可能会要求对设计的再次考虑。
Differences between versions in the EJB specification with respect to the way the container handles application exceptions may require reconsideration of the design.
您还经常需要给这些更具体的异常(这些异常也是主应用程序异常的子类)提供子类，以提供更具体的异常。
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.
在云计算环境中，编码集名称不相容会导致数据损坏、应用程序异常、系统崩溃、可移植性差和转换失败。
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.
在我描述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.
全国的计算机系统正受到一系列称做病毒的神秘的异常程序的影响。
Computer systems throughout the country are being affected by a series of mysterious rogue programs, known as viruses.
如果XML 分析程序在其输入中看到一个空字符，它就会发出异常并停止处理。
If the XML parser sees a null character in its input, it throws an exception and stops processing.
这将导致正被处理的RPG程序内部出现一个异常。
This causes an exception to occur in the RPG program being handled.
在完成了第一轮需求分析后，您手中拥有的这些叙述性说明会使程序的异常处理设计更为合理且更有价值。
With a first round of requirements analysis complete, the narrative notes you have in hand will make design of your program's exception-handling far more rational and rewarding.
但是，真正的好处在于将这种技术作为出发点，以创建特定于应用程序的异常层次结构。
The real benefit, however, is in using this technique as the starting point to create an application-specific hierarchy of exceptions.
当服务器报告一个意外的异常时，您可以检查关联堆栈跟踪的类和方法，来确定哪个应用程序导致了异常或者与异常有关。
When the server reports an unexpected exception, you can examine the classes and methods of the associated stack trace to determine which application caused, or was involved in, the exception.
其次，所有错误或意想不到的警告实际上应该由异常处理程序来处理。
Secondly, all errors or unexpected warnings really should be handled by the exception handler.
始终为消息流配备异常处理机制，而不要依赖缺省代理异常处理程序。
Always have exceptional handling mechanism for the message flows rather than relying on the default broker exception handler.
因此，在某个特定开发项目中，使用异常的第一步，也往往是最容易被忽视的一步，就是确定程序对异常的需求。
The first step in using exceptions in a particular development project, therefore, and much the most-neglected one, is to determine your program's requirements for exceptions.
重写随后执行的函数指针或异常处理程序。
Overwriting a function pointer or exception handler that is subsequently executed.
在这个阶段，SQL的执行失败，程序必须捕获异常来判断失败的原因。
At that stage, the execution of the SQL fails and the program must catch any exceptions to determine the reason for the failure.
缺省异常处理程序可以在单个被破坏的消息处理失败时阻塞消息使用。
The default exceptional handler can block the message consumption when a single poisoned message processing is failed.
注释还可以动态地提取HTTP请求中的信息，以及把应用程序生成的异常映射到http响应码。
Annotations can also dynamically extract information from HTTP requests and map application-generated exceptions to HTTP response codes.
处理多线程程序中的异常。
如果使用第二对方法设置默认处理程序，那么没有自己的异常处理程序的所有线程都将使用默认处理程序。
If the default handler is set with the latter pair of methods, any thread that doesn't have its own exception handler will use the default.
如果装载了该应用程序的系统异常繁忙，那么利用网格计算，应用程序可以在格网中空闲的或未充分利用的系统上运行。
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.
应用推荐