Message not included in ErrorAttributes for non-RuntimeExceptions about spring-boot

[philwebb]

We discussed this today as a team and we're not keen to unwrap UndeclaredThrowableException ourselves. The main reason is that UndeclaredThrowableException does have a constructor that accepts a message so we can't be sure that a user hasn't crafted a specific instance with a message that they want to use.

To solve your specific problem we recommend subclassing DefaultErrorAttributes and overriding the getMessage method. This should allow you to find the message that you want to display. If you register your own class as a bean, our auto-configuration will back off.

[f-cramer]

Does this rejection also include a rejection to change ReflectionUtils#invokeMethod(java.lang.reflect.Method, java.lang.Object) in Spring Framework, or should I create another issue there? Sorry, I don't now if the teams for Boot and Framework are the same or not.

[philwebb]

Sorry @f-cramer, I missed that part. The ReflectionUtils class is part of Spring Framework so you can make a request at https://github.com/spring-projects/spring-framework/issues/new.

I suspect that it might be declined since we don't often propagate messages when wrapping exceptions, but it can't hurt to ask.