java invoke异常,在java中设置异常原因

I can see on catching an exception that I can print e.getCause(), though it is always null.

Do I need to set it somewhere, or is something missing which is setting the cause to null?

解决方案

An Exception has the attributes message and cause. The message is a description, telling a human reader more or less exactly, what went wrong. The cause is something different: it is, if available, another (nested) Throwable.

The concept is often used if we use custom exceptions like this:

catch(IOException e) {

throw new ApplicationException("Failed on reading file soandso", e);

// ^ Message ^ Cause

}

Edit - in response to @djangofans comment.

The standard is that the nested expression (the cause) is printed with it's stack trace too.

Running this little application

public class Exceptions {

public static void main(String[] args) {

Exception r = new RuntimeException("Some message");

throw new RuntimeException("Some other message", r);

}

}

will output

Exception in thread "main" java.lang.RuntimeException: Some other message

at Exceptions.main(Exceptions.java:4)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)

Caused by: java.lang.RuntimeException: Some message

at Exceptions.main(Exceptions.java:3)

... 5 more

Both messages are included.

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值