解决template might not exist or might not be accessible by any of the configured Template Resolvers问题

最新推荐文章于 2024-04-19 10:15:39 发布
最新推荐文章于 2024-04-19 10:15:39 发布
阅读量5.2k 收藏
点赞数 1
分类专栏： springBoot-ExceptionCollection
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/baidu_36716593/article/details/86536218
版权

报错信息：

org.thymeleaf.exceptions.TemplateInputException: Error resolving template [grainType/saveOrUpdateGrainType], 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:1370) [spring-webmvc-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1116) [spring-webmvc-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1055) [spring-webmvc-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:942) [spring-webmvc-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1005) [spring-webmvc-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:908) [spring-webmvc-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:882) [spring-webmvc-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat-embed-websocket-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at com.alibaba.druid.support.http.WebStatFilter.doFilter(WebStatFilter.java:123) [druid-1.0.11.jar:1.0.11]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99) [spring-web-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:92) [spring-web-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:93) [spring-web-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:200) [spring-web-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-5.1.3.RELEASE.jar:5.1.3.RELEASE]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:791) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1417) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_131]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_131]
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.13.jar:9.0.13]
    at java.lang.Thread.run(Thread.java:748) [na:1.8.0_131]

原因分析：

首先声明一下这个问题是我在使用Spring Boot与thymeleaf模板时遇到的问题，是由于未在控制层controller方法前加注解：@ResponseBody导致，（1）当方法返回为数据时，需加@ResponseBody; （2）当返回为页面时，不需要加

Csorpio
关注
  • 1
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
springboot项目打包部署后，测试报错template might not exist or might not be accessible by any of the configure
weixin_43849269的博客
02-24 905
本人是新手，自己写的小项目在开发时进行测试正常，部署之后再测试前端页面报错如下： 我的原因就是controller层中的对应方法的返回值最前边多加了一个“/”,thymeleaf模板引擎视图解析出错。 解决方法就是去掉多余的“/”。 ...
解决 template might not exist or might not be accessible by any of the configured Template Resolvers
SELECT_BIN的博客
05-16 1万+
template might not exist or might not be accessible by any of the configured Template Resolvers 报错解决方案 org.thymeleaf.exceptions.TemplateInputException: Error resolving template "setRecommendGoods/ge...
专门解决template might not exist or might not be accessible by any of the configured Template Resolvers
最新发布
m0_68335484的博客
04-19 358
专门解决template might not exist or might not be accessible by any of the configured Template Resolvers。配置好后，然后 maven-install。再到class下面看，已经出现了报错的html。主要是由于maven打包时，没有将html打包到class里面。从旧项目上搭建了一套新项目，出现了以下错误。
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.
Error resolving template ““, template might not exist or might not be accessible by any of the confi
沧海皎珠
05-12 1073
springboot+thymeleaf项目，在获取前端传来的json数据时报错 Error resolving template “xxx”, template might not exist or might not be accessible by any of the configured Template Resolvers 可以获取到数据，但是会报错 解决办法：在获取数据的方法上添加@ResponseBody注解 个人理解：这个方法是用来区分方法的返回值字符串 和 视图解析器解析的页面名字字符串
运行Sqoop出现hcatalog does not exist!…accumulo does not exist!解决方案
01-07
有一段时间没用sqoop了，今天...Please set $HCAT_HOME to the root of your HCatalog installation. Warning: /opt/module/sqoop/bin/…/…/accumulo does not exist! Accumulo imports will fail. Please set $ACCU
Code::Blocks – The file does not exist.
01-09
Code::Blocks – The file does not exist. 1. Code::Blocks Could not open the file '/home/strong/codeblocks_work/Fire-master/src/bubble/config.cpp'. The file does not exist. 2. Build log ...... g++: ...
Centos7配置Docker镜像加速器-阿里云官方(报错解决repository does not exist or may require ‘docker login’)
01-07
我们在日常学习或者使用docker的时候可能会遇到下载安装镜像速度慢的问题,这里我们就得添加以下中国的阿里云镜像就会速度加快 添加阿里云镜像 阿里云网站 按照命令即可,也可以手动创建/ect/docker/daemon.json来用...
Django 报错User.DoesNotExist: User matching query does not exist.解决办法
01-20
models.py — 定义数据表 from django.db import models # Create your models here. class User(models.Model): username = models.CharField(max_length=20, primary_key=True) password = models.CharField(max...
Serv_U 安全设置以后出现530 Not logged in, home directory does not exist的解决方法
01-10
一般情况都是因为文件的上级目录不存在浏览权限。...详细说明：Serv_U安装设置以及530 Not logged in, home directory does not exist解决方法安装程序尽量采用最新版本，避免采用默认安装目录，设置好serv-u
错误：template might not exist or might not be accessible by any of the configured Template Resolvers
群鸿
04-15 9236
笔者在开发Java发送邮件中遇到一个非常奇怪的事情，在采用了Thymeleaf作为邮件模板时，报错如下： Error resolving template [cert/sendThymeleafMailApi], template might not exist or might not be accessible by any of the configured Template Resolv...
TemplateInputException:template might not exist or might not be accessible
cdaic的博客
05-23 1万+
Spring Boot 官网的介绍推荐的模板引擎Thymeleaf，使用上的确很方便，在IDEA或Eclipse中运行的时候，模板引入正常，但打成Jar包跑的时候，有时会报TemplateInputException
解决: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
添加点击量Springboot+redis+aop切入controller层方法截面+return String返回.html页面出现template might not exist:不是框架配置问题
qq_42664961的博客
06-01 344
Whitelabel Error Page This application has no explicit mapping for /error, so you are seeing this as a fallback. Sun May 31 23:47:56 CST 2020 There was an unexpected error (type=Internal Server Error, status=500). Error resolving template [hello], templat
接口添加@ResponseBody注解后，thymeleaf依然报错：template might not exist or might not be accessible by any of the
weixin_41594790的博客
12-08 440
先上问题代码 @Controller @RequestMapping("/guarantee") public class GuaranteeController { @Autowired private NoticeService noticeService; @RequestMapping({"", "/index"}) public ModelAndView index(ModelAndView mav){ //通知信息 mav.ad
template might not exist or might not be accessible by any of the configured Template Resolvers异常处理
weixin_46378680的博客
02-23 2463
最近在做项目时，出现这个错误，从错误提示可以看出是模板不存在的意思。 检查本地静态资源，发现profile.html存在 检查控制器，发现控制器返回的页面路径为 缺少"/",增加下划线 可以正常访问。 因此，在控制器返回页面时，如果页面放在template目录下，页面正确的路径是"/+{文件名}"！ ...
template might not exist or might not be accessible by any of the configured Template Resolvers (tem
weixin_44637331的博客
11-12 2015
错误分析：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

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值