template might not exist or might not be accessible by any of the configured Template Resolvers

最新推荐文章于 2025-03-15 12:30:21 发布
原创 最新推荐文章于 2025-03-15 12:30:21 发布 · 442 阅读 · 0 ·
本内容遵循CC 4.0 BY-SA版权协议
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
收录于
SpringBoot

当前文章被收录于：

SpringBoot
12 篇文章 0 人学习

记录了小编学习SpringBoot框架时遇到的一些问题。

订阅专栏 查看详情
本文介绍了一个关于Thymeleaf模板引擎在Spring框架中无法正确加载模板的问题及解决方案。通过在Controller方法上添加@ResponseBoby注解，成功解决了TemplateInputException异常，确保了页面的正常渲染。

 问题如下所示：

org.thymeleaf.exceptions.TemplateInputException: Error resolving template [userList], template might not exist or might not be accessible by any of the configured Template Resolvers
	at org.thymeleaf.engine.TemplateManager.resolveTemplate(TemplateManager.java:869) ~[thymeleaf-3.0.11.RELEASE.jar:3.0.11.RELEASE]
	at org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:607) ~[thymeleaf-3.0.11.RELEASE.jar:3.0.11.RELEASE]
	at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1098) ~[thymeleaf-3.0.11.RELEASE.jar:3.0.11.RELEASE]
	at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1072) ~[thymeleaf-3.0.11.RELEASE.jar:3.0.11.RELEASE]
	at org.thymeleaf.spring5.view.ThymeleafView.renderFragment(ThymeleafView.java:362) ~[thymeleaf-spring5-3.0.11.RELEASE.jar:3.0.11.RELEASE]
	at org.thymeleaf.spring5.view.ThymeleafView.render(ThymeleafView.java:189) ~[thymeleaf-spring5-3.0.11.RELEASE.jar:3.0.11.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1373) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1118) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1057) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:634) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) ~[spring-webmvc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) ~[tomcat-embed-websocket-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:93) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) ~[spring-web-5.2.2.RELEASE.jar:5.2.2.RELEASE]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) ~[tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:526) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:367) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:860) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1591) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_31]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_31]
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.29.jar:9.0.29]
	at java.lang.Thread.run(Thread.java:745) [na:1.8.0_31]

解决办法：在对应的Controller类，出现这个问题的对应方法上边添加@ResponseBoby。出现这个问题之后，也在网上找过很多其他的方法，只有这种方法解决了我的问题，传递下去，帮助更多遇到这个问题的小伙伴~~

标签
#thymeleaf template
解决Error resolving template [x] template might not exist or might not be accessible by any of the con
念兮为美
08-21 1万+
解决今天配置好shiro + jwt且正常启动spring boot后，调用auth/login登录方法时报出的错误：org.thymeleaf.exceptions.TemplateInputException: Error resolving template [auth/login], template might not exist or might not be accessible by any of the configured Template Resolvers
Thymeleaf Error resolving template [index],template might not exist or might not be accessible问题解决
旭东怪的博客
08-29 1万+
问题描述： # 后缀 spring.thymeleaf.prefix=classpath: /templates # 模板格式 spring.thymeleaf.mode=HTML5 spring.thymeleaf.encoding=UTF-8 spring.thymeleaf.content-type=text/html spring.thymeleaf.suffix=.html # 开发时关闭缓存,不然没法看到实时页面 spring.thymeleaf.cache=false 以上为我的thym
swagger-ui.html渲染出错：Please indicate a valid Swagger or OpenAPI version field
giser@2011的博客
07-21 3467
swagger-ui.html报错， The provided definition does not specify a valid version field. Please indicate a valid Swagger or OpenAPI version field. Supported version fields are swagger: "2.0" and those that match openapi: 3.0.n (for example, openapi: 3.0.0).
Error resolving template [login], template might not exist or might not be accessible by any of 问题
你好_晴天
10-21 5655
Error resolving template [login], template might not exist or might not be accessible by any of 问题
Error resolving template [login], template might not exist or might not be accessible by any of the
m0_53249319的博客
12-05 7021
Error resolving template [login], template might not exist or might not be accessible by any of the configured Template Resolvers 外部引入templates的模板资源后，测试访问显示错误： @GetMapping("login") public String login(){ return "login"; } 解决方法： 找一下配置
template might not exist or might not be accessible by any of the configured Template Resolvers
刘大猫
05-16 1万+
文章目录想实现效果报错报错原因有x以下种第1种场景错误：未设置返回格式第2种场景错误：html未打包进去（我的就是这种错误导致的）第3种场景错误：路径名写错了(网上摘抄未验证过)第4种场景错误：在使用springboot的过程中，如果使用thymeleaf作为模板文件，则要求HTML格式必须为严格的html5格式，必须有结束标签，否则会报错。(网上摘抄未验证过)第5种场景错误：模板使用thymeleaf时pom引入不正确(网上摘抄未验证过)第6种场景错误：如果使用了视图解析器，检查视图跳转WebMvcCo.
解决:template might not exist or might not be accessible by any of the configured Template Resolvers报错
热门推荐
weixin_53106424的博客
03-15 5万+
问题描述：   Spring Boot 项目访问resources/templates下静态资源文件报500错误，如果页面显示404错误一定是你地址写错了。 报错内容： Servlet.service() for servlet [dispatcherServlet] in context with path [/test] threw exception [Request processing failed; nested exception is org.thymeleaf.exceptions.Tem
报错：template might not exist or might not be accessible by any of the configured Template Resolvers
qq_29062045的博客
09-14 4889
springboot使用thymeleaf报错： org.thymeleaf.exceptions.TemplateInputException: Error resolving template [index], template might not exist or might not be accessible by any of the configured Template Resolvers 详细报错如下： org.thymeleaf.exceptions.Templat...
解决template might not exist or might not be accessible by any of the configured Template Resolvers问题
Csorpio's blog
01-18 5465
报错信息： org.thymeleaf.exceptions.TemplateInputException: Error resolving template [grainType/saveOrUpdateGrainType], template might not exist or might not be accessible by any of the configured Templat...
template might not exist or might not be accessible by any of the configured Template Resolvers (tem
weixin_44637331的博客
11-12 2274
错误分析：template might not exist or might not be accessible by any of the configured Template Resolvers ...... 原因一 /*controller*/ @GetMapping("/") public String index(){ log.warn("访问了首页..."); return "index"; } @GetMapping
错误：template might not exist or might not be accessible by any of the configured Template Resolvers
群鸿
04-15 9498
笔者在开发Java发送邮件中遇到一个非常奇怪的事情，在采用了Thymeleaf作为邮件模板时，报错如下： Error resolving template [cert/sendThymeleafMailApi], template might not exist or might not be accessible by any of the configured Template Resolv...
template might not exist or might not be accessible by any of the configured Template Resolvers报错
m0_68335484的博客
06-07 2683
template might not exist or might not be accessible by any of the configured Template Resolvers报错
关于template might not exist or might not be accessible by any of the configured Template Resolvers
最新发布
weixin_42242607的博客
03-15 1013
template might not exist or might not be accessible by any of the configured Template Resolvers
template might not exist or might not be accessible by any of the configured Template Resolvers解决办法
最帅程序猿的博客
07-25 949
在 Spring MVC 中，@Controller 用于定义控制器类，而 @ResponseBody 用于将方法的返回值直接写入 HTTP 响应体中，而不是返回一个视图。@RestController 是 Spring Framework 提供的一个注解，用于定义控制器类，其返回的每个方法的结果都直接写入 HTTP 响应体中，而不是依赖于视图解析器来解析视图。：所有方法都会默认添加 @ResponseBody 注解，使其返回的对象直接写入 HTTP 响应体中，而不是寻找对应的视图。
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

zqq_2016

有用的话，来打赏博主吧

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值