Exception thrown inside catch block - will it be caught again?(在 catch 块内抛出异常 - 它会再次被捕获吗?)
问题描述
这似乎是一个编程 101 问题,我原以为我知道答案,但现在发现自己需要仔细检查.在下面这段代码中,第一个catch块中抛出的异常会被下面的通用Exception catch块捕获吗?
This may seem like a programming 101 question and I had thought I knew the answer but now find myself needing to double check. In this piece of code below, will the exception thrown in the first catch block then be caught by the general Exception catch block below?
try {
// Do something
} catch(IOException e) {
throw new ApplicationException("Problem connecting to server");
} catch(Exception e) {
// Will the ApplicationException be caught here?
}
我一直认为答案是否定的,但现在我有一些可能由此引起的奇怪行为.大多数语言的答案可能都是相同的,但我正在使用 Java.
I always thought the answer would be no, but now I have some odd behaviour that could be caused by this. The answer is probably the same for most languages but I'm working in Java.
推荐答案
不,因为新的 throw
不在 try
块中直接.
No, since the new throw
is not in the try
block directly.
这篇关于在 catch 块内抛出异常 - 它会再次被捕获吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:在 catch 块内抛出异常 - 它会再次被捕获吗?


基础教程推荐
- 无法复制:“比较方法违反了它的一般约定!" 2022-01-01
- Spring AOP错误无法懒惰地为此建议构建thisJoinPoin 2022-09-13
- 使用堆栈算法进行括号/括号匹配 2022-01-01
- 存储 20 位数字的数据类型 2022-01-01
- Struts2 URL 无法访问 2022-01-01
- 问题http://apache.org/xml/features/xinclude测试日志4j 2 2022-01-01
- REST Web 服务返回 415 - 不支持的媒体类型 2022-01-01
- 修改 void 函数的输入参数,然后读取 2022-01-01
- 如何对 Java Hashmap 中的值求和 2022-01-01
- RabbitMQ:消息保持“未确认"; 2022-01-01