在这个类中，定义服务器操作完成时客户机页面如何处理数据(或异常)。
In this class, you define what the client page does with the data (or the exception) when the server is done.
最后一个流控制标记是 <c:catch> ，它允许在JSP页面内进行初级的异常处理。
The final flow-control tag is <c:catch>, which allows for rudimentary exception handling within a JSP page.
允许servlet容器处理异常的问题在于，这严重限制了错误页面上显示的内容，并且禁止了事务回滚。
The problem with allowing the servlet container to handle exceptions is that it severely limits what can be displayed on the resulting error page and makes transactional rollbacks all but impossible.
一旦出现未处理的异常，就显示该缺省的错误页面。
The default error page will be displayed whenever an unhandled exception occurs.
如果在处理jsp页面时有一个异常抛出的话，exception对象就会立即通过隐式声明的exception变量的方式抛给指定的错误页面。
Whenever an exception is thrown while processing your JSP page, the exception object will immediately be thrown to the designated error page by means of the implicitly declared exception variable.
NET有一个顶级异常处理程序，该处理程序在对异常进行处理时向浏览器用户显示错误页面。
NET has a top-level exception handler that handles exceptions to show error pages to browser users.
第八部分添加联系页面、关于页面和异常处理，也是对整个系列的总结。
Part 8 adds a contact page, about page, and exception handling. This is the conclusion of the series.
第八部分添加联系页面、关于页面和异常处理，也是对整个系列的总结。
Part 8 adds a contact page, about page, and exception handling. This is the conclusion of the series.
应用推荐