About special case: This application has no unequivocal mapping for/blunder, so you are considering this to be a fallback.
The area of the Application startup class is wrong. To put the Application class on the furthest side, that is, to incorporate all sub-bundles
Cause: Spring-boot will naturally stack all segments under the bundle of the startup class and its sub-bundles.
In the springboot design record: application.yml or application.properties about the arrangement of the view resolver:
At the point when the spring-boot-starter-paren form under the pom record is high:
spring.mvc.view.prefix/spring.mvc.view.suffix (springBoot made as a matter of course utilizes this mode)
At the point when the spring-boot-starter-paren form under the pom record is low:
Controller URL way composing issue
The genuine access way does not coordinate "xxx". [You can pass judgment on the accuracy of the way by yielding a sentence in the controller]
On the off chance that your task is springBoot, the best approach to bundle it is as war bundle, the arrival estimation of the controller is a string, you have to discover the parse into jsp page, you should focus on pom Whether the tomcat-implant jasper reliance is added to the record