-
Notifications
You must be signed in to change notification settings - Fork 40.2k
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
SpringBoot 3.0.3 can't identify any @RestController anotated class except in Startup Class #34382
Comments
Closing as a duplicate of #34379 |
I have the same issue with spring boot 3.0.3 using Ubuntu, I'm not sure if it is specific to Windows. Previously I was using Spring Boot 3.0.2 and had no problems. |
spring boot 3.0.4 still has this problem |
@softboy99 Please ensure that you're using Spring Framework 6.0.6 as that's where the fix was made. If you still have a problem when using Spring Framework 6.0.6 please open a Spring Framework issue and provide a minimal sample that reproduces the problem. |
Spring Boot 3.0.4 shiped with Spring Framework 6.0.6, on the spring official website, it's said |
@softboy99 Yes, that's correct, but we have no way of knowing if that's the version that your application is actually using. Something may have overridden Spring Boot's dependency management. As I said above, if you can reproduce the problem with Spring Boot 3.0.4 and Spring Framework 6.0.6, please open a Spring Framework issue and provide a minimal sample. |
SpringBoot version:
3.0.3
OS:
Windows 11
Java:
OpenJDK 19
Recently I just wrote a simple Spring Boot application.
And I used the latest Spring Boot and the version is 3.0.3.
What I did is I wrote a simple controller, but I found Spring boot can't identify this.
But if I put the simple mapping in startup class, it can work.
The code is simple as below:
The startup class:
Base on my setting, it should have 2 mapping which is
/hello
and/hello/hello
.Actually, it only can find the first one written in startup class
But it's work in Spring boot
2.7.9
The text was updated successfully, but these errors were encountered: