Handling user errors and application exceptions.
处理用户错误和应用程序异常。
Conversely, application exceptions under EJB 1.0 automatically caused a transaction rollback under certain circumstances.
反过来说，EJB 1.0下发生的应用程序异常在某种环境下会自动导致一个事务回滚。
The container must pass application exceptions through to the EJB client without changing the exception nor changing the transaction.
容器必须将应用程序异常传递到EJB客户端并且不改变该异常以及事务。
I think this is rather inconsistent, that system exceptions cause automatic rollback while application exceptions specifically do not.
我认为这是非常矛盾的，系统异常引发了自动回滚而应用程序异常不能。
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.
在我描述JAX - RPC异常处理时，我将更深入地看一下语义上的意思以及应用程序异常之间的关系(在WSDL的上下文环境里)。
But, more importantly, although the technique of intercepting application exceptions is well-known, is it really appropriate in case of Web services invocations?
但更重要的是，尽管拦截应用程序异常的技术广为人知，但它真的适合于Web服务调用吗？
Differences between versions in the EJB specification with respect to the way the container handles application exceptions may require reconsideration of the design.
与容器处理应用程序异常的方式有关的EJB规范的版本之间的差别可能会要求对设计的再次考虑。
In a cloud computing environment, problems with code-set name compliance can cause data corruption, application exceptions, system crashing, poor portability, and conversion failures.
在云计算环境中，编码集名称不相容会导致数据损坏、应用程序异常、系统崩溃、可移植性差和转换失败。
Exceptions can be dealt with in two ways: The architects can impose limitations and constraints on the architecture of the new application so that it follows the existing architectural constructs.
可以通过两种方式来处理异常情况：架构师可以对新的应用程序的体系结构强加一些限制和约束，使其遵循现有的体系结构构造。
Application code also tends to catch and translate exceptions, usually discarding many details in the process.
应用程序代码也往往捕获并转换异常，其间常常废弃许多详细信息。
Exceptions raised in callbacks that were not properly handled or caught by a global handler would silently terminate the application, without any indication of the problem.
回调中所抛出的异常如果没有被全局处理器处理或捕获，那么他们会终止应用，并不会给出任何关于问题的提示信息。
If your answer is that it is common, you run a greater risk of stale data exceptions, making this strategy a poor choice for your application profile.
如果您的回答是常见，则面临着极高的失效数据异常风险，那么这个策略对于您的应用程序探查来说是一个很差的选择。
Once started, it will alert the user to unhandled application and data-binding exceptions via a floating window.
启动后，它会通过一个浮动窗口通知用户未处理的应用与数据绑定异常。
When components throw application errors, they could log the exception at the appropriate interface within the component boundaries and then throw the exceptions.
当组件抛出应用出错时，他们可以在组件边界内通过适当的接口记录异常，然后再抛出异常。
Application-level exceptions result from incorrect message semantics or logical errors within the application.
应用级异常，由于错误的消息语义或应用中的逻辑错误导致。
You should get a clean run without exceptions, and will see the following in the console window after the application finishes its run: Getting the InitialContext...
您应当顺利地运行而不出现异常，当应用程序运行结束后，您将在控制台窗口中看到以下输出。
Remote and naming exceptions are system-level exceptions, whereas application and invalid-data exceptions are business-level exceptions, because they deliver more applicable business information.
远程和命名异常是系统级异常，而应用程序和非法数据异常是业务级异常，因为它们提交更适用的业务信息。
For a BPM application, business and process exceptions may need different handling mechanisms.
对于BPM应用程序，业务和流程异常可能需要不同的处理机制。
Of course, many exceptions to this rule have popped up based on specific application needs.
当然，基于一些特定的应用需求，该规则也有许多例外。
You should handle exceptions coherently throughout the application.
应该在整个应用程序中一致地处理异常。
If I'm performing the same iteration while running in an application server, I'm not nearly as cavalier about letting the exceptions go uncaught.
如果我在运行应用服务的同时执行相同的迭代，我不能对这些异常坐视不管。
Tracing exceptions wherever they are caught ensures that valuable stack trace information can still be extracted from a production application.
跟踪异常(无论它们在何处捕获)保证了有价值的堆栈跟踪信息仍然可以从生产应用程序中抽取。
Not to mention that cloud providers need the ability to handle production exceptions, manage application and workload service levels and resources, and schedule activities without human intervention.
更不用说，云计算提供商必须能够在没有人工干预的情况下处理生产意外、管理应用程序和工作负载服务水平和资源以及调度活动。
The network faults framework provides developers with an API that categorizes network exceptions passed to it by an application.
网络故障框架提供给开发人员一个API，此 API 可以分类由应用程序传递给它的网络异常。
At the same time, your application code may need to access the information within these exceptions, so you can't simply throw out or ignore them.
同时，应用程序代码可能需要访问这些异常中的信息，因此不能轻易地抛弃或忽略它们。
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.
您还经常需要给这些更具体的异常(这些异常也是主应用程序异常的子类)提供子类，以提供更具体的异常。
Exceptions or compiler diagnostics are passed to the log method or written directly into the scrollable errors component in the application.
异常或编译器诊断信息被传递给log方法或直接写入到应用程序中可滚动的errors组件。
When running in an application server environment, these exceptions will typically be contained in one or more First Failure Data Capture (FFDC) records.
当在应用服务器环境中运行时，这些异常一般包含在一个或多个FirstFailureDataCapture (FFDC)记录中。
With a simple sample application, the method was proven to function without any concurrency exceptions using Apache JMeter to test the access.
用一个简单的样例应用程序证明该方法可在没有任何并发性异常的情况下使用ApacheJMeter测试存取。
It also means you can combine Web services as a composite application using one WSDL in which you can switch protocols or locations under various conditions and exceptions.
还意味着您可以通过wsdl将web服务结合复合成应用程序，在WSDL中您可以在各种条件和异常情况下切换协议和位置。
应用推荐