全部

1·The developer must specify where and when to roll back a transaction when a checked exception occurs.

开发人员必须指定出现异常时在何处以及何时回滚事务。

2·Checked exceptions inherit from exception class and are used to handle recoverable errors such as business error scenarios.

已检查异常继承自exception类并用于处理可恢复性出错诸如业务出错场景。

3·One way to handle this is to provide a public static initialize method that throws a checked exception when initialization fails.

处理这个问题的一种方法是提供一个公共静态initialize方法，初始化失败时该方法将抛出一个检查到的异常。

4·Methods in the DAO interface should throw checked exceptions only if the caller can reasonably be expected to handle the exception.

只有在可以合理地预期调用者可以处理异常时，DAO 接口中的方法才应该抛出检查过的异常。

5·The container will not automatically roll back a transaction on a checked exception when you use the Declarative Transaction model.

在使用 Declarative Transaction 模型时，容器将不会针对检测到的异常自动回滚事务。

6·This checked exception — the only one defined by the scripting package — indicates that the engine failed to parse or execute the given code.

这个选中的异常(脚本包中定义的惟一一个异常)表示引擎无法解析或执行给定的代码。

7·When a method throws InterruptedException, it is telling you several things in addition to the fact that it can throw a particular checked exception.

当一个方法抛出InterruptedException时，它不仅告诉您它可以抛出一个特定的检查异常，而且还告诉您其他一些事情。

8·The answer, surprisingly, is that upon a checked exception (either in the Spring Framework or EJB), the transaction commits any work that has not yet been committed.

答案出乎意料：根据受控异常(不管是在Spring Framework中还是在EJB中)，事务会提交它还未提交的所有工作。

9·Using Listing 13, this means that if a checked exception occurs during the updateAcct method, the trade order is persisted, but the account isn't updated to reflect the trade.

使用清单13，这意味着，如果在执行updateacct方法期间抛出受控异常，就会保存交易订单，但不会更新帐户来反映交易情况。

10·If you invoke a preexisting function that can throw a checked exception, you should write a wrapper function that catches and handles that exception; then, invoke the wrapper method from XSLT instead.

如果您调用一个可能抛出检查异常的已有函数，您应编写一个包装器函数，捕获并处理此类异常，然后在XSLT中调用包装器方法。