-
Notifications
You must be signed in to change notification settings - Fork 37.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When configuration class parsing fails, provide more information about the class that triggered the failure #31146
Comments
Looking at the related issue, the root exception message seems to be:
However, I don't see how this would be possible as the error message has additional brackets with the bean class name for a very long time. Lines 177 to 178 in 8404537
I wonder if the OP in the boot issue hasn't tempered the exception message. |
I have reproduced the problem and I can confirm that there is a class name. However, it is not the right class name:
It should be @Configuration
public class TestConfiguration extends WebSecurityConfigurerAdapter { } |
The revised exception message now looks as follows:
|
Affects: 5.3 and later
See spring-projects/spring-boot#37153 for some background. In this case parsing has failed because a configuration class extends a class that doesn't exist. While the offending class can probably be identified using a debugger, it would be helpful if more information was included in the log message. In this case, the fully qualified name of the configuration class whose super-class is being processed would pinpoint the problem.
The text was updated successfully, but these errors were encountered: