由于此代码仅仅作为样例使用，我们没有执行任何实际的错误处理，但是我们实现了一个虚构的异常处理程序，从而完成代码的编译。
Because this code is only a sample we don't perform any real error processing, but we do implement a dummy exception handler to allow the code to compile.
其次，所有错误或意想不到的警告实际上应该由异常处理程序来处理。
Secondly, all errors or unexpected warnings really should be handled by the exception handler.
注意，SQLPL中适当的异常处理要求每个过程有一个错误处理程序，这个错误处理程序应该可以很容易地告诉我们出错的过程。
Note that proper exception handling in SQL PL dictates that each procedure has an error handler that could easily enough have told us the failing procedure.
为程序提供有意义的错误信息的最简单方法是，自己创建异常类并传递给SAXException。
The easiest way to provide meaningful error information to your program is to build your own exception that you can pass to SAXException.
continue继续报告错误，但它并不异常终止(ABEND)该程序。
Continue continue reports errors, but it doesn't ABEND the program.
我们可以使用initactiontype[3]方法来注册执行动作时可能发生的异常，以及它们的类型和错误信息，并为执行程序本身执行初始化操作。
InitActionType [3] metod can be used to register possible exceptions while executing the action, along with their type and error message and do initial initialization for the executor itself.
这在这里它是一个try程序块,它报出异常，但他不是io错误。
That says it's in here. It's in this tri-block. It raised an exception, but it wasn't and I O error.
没有错误消息(各地的程序员请注意，异常堆栈跟踪不能当作真正的错误消息，有时，eXist甚至连堆栈跟踪都没有提供给您)。
Error messages are nonexistent. (Note to programmers everywhere: Exception stack traces don't count as decent error messages — and sometimes exist doesn't even give you those.)
如果执行了此操作，并且活动再次失败，则该异常会传播到该流程的错误处理程序，并且该活动不会再停止。
If this is done and the activity fails again, the exception is propagated to the fault handling of the process and the activity is not stopped again.
如果这个异常没有被捕捉到，它将立即关闭应用程序，并将一条错误消息和栈跟踪输出到控制台。
If this exception isn't caught, it will immediately kill the application with an error message and stack trace dumped to the console.
本节向您展示了如何编写一个程序来缓存可能出现的异常，如果WAS ND本身出现错误且在纠正自己的错误时就会出现这样的异常。
This section has shown how you can write a program that catches the likely exceptions that will occur if WAS nd itself has experienced a fault and is undergoing its own fault corrections.
某些派别的信徒支持使用异常来检查参数和其他的前置条件，使用错误编码来报告程序中出错的处理。
Some disciples espouse using exceptions to check parameters and other preconditions, and error codes to report processing errors within the function.
一般情况下，DOM实现必须检验操作的正确性，并在应用程序传递错误参数或者执行非法操作时抛出异常。
Normally, a DOM implementation must verify the correctness of operations and throw an exception if an application passes the wrong parameters or performs an illegal operation.
事件处理程序采集的信息必须编码在一个错误信息中，该错误信息包装在一个异常对象中提交给解析器客户。
The information gathered by the event handler must be encoded in an error message that's wrapped in an exception object and posted to the parser's client.
客户中一个专门的错误处理程序接收这种异常，并且必须在解析器错误消息中检索出需要的信息！
A special error handler in the client receives this exception and must parse the parser's error message to retrieve the required information!
异常中还显示了通信错误，可以看到，在这种特定情况下，这就是要返回给应用程序的内容。
The communication error is also displayed in the exception, and you can see that in this particular case this is what is being returned back to the application.
当你的应用程序发生一个错误或者抛出一个异常时，FFDC可以确保这个错误或者异常被正确的处理，并且任何和这个错误相关的信息都将会被保存下来。
When an error or exception occurs in your application, FFDC ensures that it is dealt with in the correct way, and that any useful information about the error is preserved.
如果服务线程因编程错误而没有处理某个异常，则会造成整个应用程序崩溃。
If a service thread does not handle an exception due to programming error, it will kill the whole application.
当流程在运行过程中出现问题或发生异常情况时，可以使用错误处理程序撤消发生错误的范围中的部分工作或未成功完成的工作。
When a problem or exceptional situation occurs while a process runs, you can use a fault handler to undo partial and unsuccessful work for the scope in which the fault occurred.
另外，对于程序员，请注意在用例中根本不要出现严重的致命错误——这种错误会导致抛出异常。
Also, for you programmer types, note that serious fatal errors — the sorts of things that would cause exceptions to be thrown — don't appear in the use cases at all.
当一个可补偿的并且长期运行的流程被异常的完成时，也就是说，当流程的错误处理程序被定位时，流程的补偿操作就会被启动。
When a compensable, long-running process is completed abnormally, that is, the fault handler of a process is navigated, process compensation is started.
Web服务业务流程执行语言(Web Services Business Process Execution Language, WS -BPEL)标准提供了错误处理程序和补偿处理程序，用于在您的业务流程逻辑中建模故障和异常路径。
The Web Services business process Execution Language (WS-BPEL) standard offers fault handlers and compensation handlers to model failure and exceptional paths in your business process logic.
errorMsg——错误消息，包括xml解析器和JCC驱动程序抛出的任何异常。
ErrorMsg — error messages, including any exception thrown by the XML parser and the JCC driver.
errorMsg——错误消息，包括xml解析器和JCC驱动程序抛出的任何异常。
ErrorMsg - error messages, including any exception thrown by the XML parser and the JCC driver.
注意，如果没有指定错误处理程序，则默认的实现对任何验证错误都抛出SAXParseException异常。
Note that if no error handler is attached, the default implementation throws a SAXParseException on any validation error.
处理用户错误和应用程序异常。
使用不需检查运行时异常来报告严重的、无法预期的错误，这可能指出程序逻辑中的错误。
Use unchecked, run-time exceptions to report serious unexpected errors that may indicate an error in the program's logic.
请注意，如果提供程序发出的HTTP响应有错误，则尝试获取HTTP响应InputStream将导致出现异常。
Note that if there is an error in the HTTP response from the provider, the attempt to get the HTTP response InputStream causes an exception.
否则，发生中断以find（查找），并且异常处理程序发出标准的file not found（文件未找到）错误。
Otherwise, a trap occurs for find, and the exception handler emits the standard file not found error.
在设计良好的系统中，异常是程序错误处理的一部分。
In well-designed systems, exceptions represent a subset of the program's error handling.
应用推荐