异常管理可以通过注释指定，或者在配置文件中指定。
Exception management is designated either through annotations or in a configuration file.
JSF规范完全忽视异常管理，将责任完全放在servlet容器上。
The JSF specification completely disregards exception management, placing its responsibility entirely on the servlet container.
这将导致所有主要的异常管理元素“服务化”[4]，（即，日志，异常解决和通知）。
This leads to "servicizing" all of the major elements of exception management [4], (i.e., logging, exception resolution and notifications).
SCA运行时异常——由SCA运行时引发，指示组件的异常管理及与远程服务的交互中存在的问题。
SCA runtime exception — thrown by the SCA runtime and signals problems in the management of the execution of components, and in the interaction with remote services.
解决横切关注点的组件，例如异常管理与规范（Instrumentation）就是这一常用功能的典型例子。
The Components to address cross-cutting concerns, for instance Exception management and instrumentation are examples of this common functionality.
这些服务包括：acid事务，补偿活动(compensatingactions)，异常管理和过程跟踪。
These services include ACID transactions, compensating actions, exception management and process tracking.
同时也请记住访问Linux专区的脚本编制诊所(Scripting clinic)论坛讨论异常管理的技术细节。
Also, remember to visit the Linux zone's Scripting clinic forum to discuss technical details of exception management.
经营管理中我们借鉴《论语》中所言的“不二过”，就是同样的错误不犯第二次，在管理学上叫做“异常管理”。
We referent the Analects in our business management, which said "No second", that means the same mistake never happen again, called "Abnormal management" in management science.
这种异常关闭阻止设备被另一个管理员实例管理。
This abnormal shutdown prevents the device from being managed by another manager instance.
如果您没有实现事务管理，则会在使用窗体设计器时获得一些有趣的异常。
If you don't implement transaction management, you will get some interesting exceptions while you work with the forms designer.
类型构造函数的另一个独特行为是运行库管理类型构造函数中的异常的方式。
Another behavior unique to type constructors is how the runtime manages exceptions in a type constructor.
随着时间的推移，消息在此异常目的地积累，您可以使用管理控制台浏览队列中的消息数。
Over time, messages accumulate at this exception destination, and you can browse the number of messages in the queue using the admin console.
这对我们来说是一项艰巨的集成任务，而且曝露了不少难以解决的微妙问题，比如异常处理、并发性、安全性、以及持久性上下文管理。
This was a difficult integration task for us, and exposed several subtle issues that were difficult to address like exception handling, concurrency, security, and persistence context management.
在J2EE管理的环境中，使用程序化接口将会导致异常。
In a J2EE managed environment, use of the programmatic interface will result in an exception.
如果野村股价因此出现异常波动，该行管理层未来几天或将面临考验。
That could test Nomura's management in coming days if the share price behaves erratically as a result.
服务管理监视服务通信量决定业务级别异常，并将它们报告给日志服务，它将它们和其它任何系统中的异常等同对待。
Service Management monitors services traffic to determine business-level exceptions and reports them to the logging service, which treats them the same way as any other exceptions in the system.
一个类似的异常和通知方法适合于管理操作遵从性(比如说满足规则)。
A similar exception and notification approach works for managing operational compliance (such as to meet regulations).
另一个好的实践是捕获所有的异常，并后退以报告unknown服务状态，以便Nagios能够正确地管理有关这个情况的通知。
Another healthy practice is to catch all exceptions and fall back to reporting UNKNOWN service status so that Nagios can manage notification of this fact appropriately.
使用这个RubyAPI，无需打开或关闭文件，也无需管理异常。
Using the Ruby API, you don't need to open or close your file or manage the exceptions.
在问题服务器的SystemOut . log文件中找到问题期间发生的与您的情况相关的异常(例如，安全性或管理控制台)。
Find an exception during the problematic time that can be related to your situation (for example, security or administrative console) in the problem server's SystemOut.log file.
您需要管理这样的异常：每当所选的库不存在时就会抛出该异常。
You need to manage the exception that is thrown whenever the chosen library is not present. The example, then, has to be updated.
这种方法的一个问题在于它需要XXL(这是一个给c添加异常处理和资源管理支持的库)，因此您实际上要仅为了处理字符串而引入一个重要的库。
One issue is that it requires XXL (a library that adds support for exception handling and asset management to c), so you do bring in significant libraries just to handle strings.
部署管理器服务器已启动，且系统输出和错误日志中未记录任何异常或错误消息。
The deployment manager server starts, without any unexpected exceptions or error messages in the system output and error logs.
本章还提供了服务版本管理、安全、异常处理与日志、管理与监测等企业解决方案关键方面的重要分析讨论。
The chapter also offers important discussion on service versioning, security, exception handling and logging, and management and monitoring, which are all important aspects of enterprise solutions.
PODS队列管理器控制输入队列、异常队列和复制队列。
The PODS queue manager operates with an input queue, exception queue, and replication queue.
用标出异常的方法，为那些有助于持续改善业务流程和管理企业的关键用户提供警报，这些异常在此后可被收集起来，以找到解决的办法。
Provide alerts to key users that facilitate the continuous improvement of business processes and assist in managing the enterprise by noting exceptions that can then be summoned for resolution.
事件中收集的数据可以用来警告管理员应该注意某些异常情况。
Data collected in an event can be used to alert administrator should anomalies show up.
最佳实践表明，异常处理应该包含重试逻辑(如果可能)，或者将任务路由给管理员处理。
Best practice indicates that exception handling should include retry logic (where possible) or routing the task to an administrator to resolve.
最后，本文列出了可能发生的错误条件，并说明如何从操作的角度识别它们(失败事件管理器、异常队列等等)。
Finally, it highlights the error conditions that can occur and shows how they can be identified (Failed Event Manager, Exceptions Queues, and so forth) from an operational point of view.
然而，它的确会告诉代码管理员，某个程序员的注释是极其简洁的、异常冗长的还是对非编程人员来说是很难理解的。
It does, however, tell the code manager if comments from a programmer are unusually terse, unusually verbose, or difficult for a nonprogrammer to understand.
应用推荐