Error resolving template，template might not exist or might not be accessible by any of the configure...

最新推荐文章于 2022-04-21 15:39:57 发布
原创 最新推荐文章于 2022-04-21 15:39:57 发布 · 2k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文探讨了在Spring Boot应用中使用Thymeleaf模板引擎时遇到的常见错误templatemightnotexistormightnotbeaccessible。文章详细分析了错误原因，涉及配置问题、模板路径错误及Thymeleaf版本不兼容等，并提供了有效的解决方案，如检查配置文件、确认模板位置正确以及确保依赖版本匹配。 
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:1371) [spring-webmvc-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1117) [spring-webmvc-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1056) [spring-webmvc-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:942) [spring-webmvc-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1005) [spring-webmvc-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:897) [spring-webmvc-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:634) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:882) [spring-webmvc-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat-embed-websocket-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99) [spring-web-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:118) [spring-web-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:92) [spring-web-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:118) [spring-web-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:93) [spring-web-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:118) [spring-web-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:200) [spring-web-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:118) [spring-web-5.1.9.RELEASE.jar:5.1.9.RELEASE]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:853) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1587) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_144]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_144]
    at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.22.jar:9.0.22]
    at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]

2019-10-11 14:12:28.378 ERROR 6036 --- [nio-8080-exec-1] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.thymeleaf.exceptions.TemplateInputException: Error resolving template [<!DOCTYPE HTML>
<html>
 ": Error resolving template [<!DOCTYPE HTML>
<html>
<head>

报错原因：

是由于问题所在与解析问题，返回给

@RequestMapping(value = "/to_list" ,produces = "text/html")

    public String list(Model model, MiaoshaUser user, HttpServletRequest request, HttpServletResponse response) {
        model.addAttribute("user", user);
        //查询商品列表
        List<GoodsVo> goodsList = goodsService.listGoodsVo();
        model.addAttribute("goodsList", goodsList);
        String html = redisService.get(GoodsKey.getGoodsList, "", String.class);
        if (!StringUtils.isEmpty(html)){
            return html;
        }


        WebContext ctx = new WebContext(request,response,request.getServletContext(),
                request.getLocale(),model.asMap());
        html =thymeleafViewResolver.getTemplateEngine().process("goods_list",ctx);
        return html;
    }

返回浏览器是这个html，那么就需要以html形式返回，所以需要加上@responsebody来

servlet.service() for servlet [dispatcherservlet] in context with path [] th
计算机毕业论文源码，学生个人网页制作html源码。贴近用户做网络推广和互联网优化。
05-25 2万+
.Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.web.client.ResourceAccessException: I/O error on GET request for "http://localhost/8081:user/1":
Servlet.service() for servlet [dispatcherServlet] in context with path [] th报错
计算机毕业论文源码，学生个人网页制作html源码。贴近用户做网络推广和互联网优化。
08-31 1万+
Servlet.service() for servlet [dispatcherServlet] in context with path [] th报错修改方法： 1、加上@Autowired注解。 2、当你检查了注解没有问题的时候，一定要先检查数据库连接，url是否写对，用户名，密码是否正确。这些常见事情往往是错误的源头。 可能出错的地方： 1.controller层没有加@ResponseBody 2.Service层实现类未添加注解@Autowired 3.@RestController使用成了
Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception
01-20
2020-04-27 22:15:44.892 ERROR 13764 --- [nio-8081-exec-9] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is java.lang.NullPointerException] with root cause java.lang.Nul
Error resolving template template might not exist or might not be accessible by any of the Template
yuzx88的博客
12-03 3643
1. 首先看报错信息 Whitelabel Error Page This application has no explicit mapping for /error, so you are seeing this as a fallback. Tue Dec 03 09:20:49 CST 2019 There was an unexpected error (type=Internal Se...
Servlet.service() for servlet [dispatcherServlet] in context with path [] th
热门推荐
weixin_44153063的博客
05-11 32万+
控制台报错信息 Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is java.lang.NullPointerException] with root cause e 1.controller层没有加@ResponseBody 2.Service层实现类未添加注解@Autowired 记
Node.js v12.16.2 的命令行选项（Command Line Options）允许用户定制运行时环境的行为
BLOG域名:programb.blog.youkuaiyun.com
04-16 1944
Node.js v12.16.2 的命令行选项（Command Line Options）允许用户定制运行时环境的行为。其中一项重要的选项是。这个选项设置默认为，这是从Node.js 12.x版本开始的标准。然而，这个选项的存在是为了向后兼容旧版的Node.js，允许用户强制使用更安全的TLS版本1.3，即使在那些不自动升级到最新标准的环境中。具体来说，如果你想要在启动Node.js时指定这个选项，你可以这样操作： 这会确保你的脚本在连接到支持TLS 1.3的服务器时能获得最佳安全性。Node.js 提供了
在Node.js v12.16.2中，`Process` 对象代表运行中的JavaScript进程，它与操作系统进程有直接联系
BLOG域名:programb.blog.youkuaiyun.com
04-16 1552
每一个启动的 Node.js 脚本都会创建一个新的操作系统级线程或者多线程模型下的工作单元——即所谓的“进程”。: 它用于在当前环境中创建一个新的JavaScript运行环境，新环境拥有自己的独立内存空间。这是实现多线程的一种方式。对象代表了一个运行中的 Node.js 应用程序实例，并且其行为直接映射到操作系统的底层进程机制。: 如前所述，这个方法用于执行一个命令并接收其输出，适合于一次性操作，而不是需要持续交互的情况。对象是一个特殊的内置模块，用于提供关于当前 Node.js 进程的信息和控制方法。
Node.js v12.16.2 的文件系统模块（`fs`）提供了用于文件和目录操作的 API
BLOG域名:programb.blog.youkuaiyun.com
04-16 605
这些是 Node.js v12.16.2 文件系统模块的一些基本用法。更多详细信息可以参考。）提供了用于文件和目录操作的 API。Node.js v12.16.2 的文件系统模块（
Hadoop_3.X.x 注意事项
底层码农
03-31 1万+
hadoop3 hdfs web端口改为9870 <property> <name>dfs.namenode.http-address</name> <value>0.0.0.0:9870</value> <description> The address and the base port where...
ZooKeeper Administrator‘s Guide：A Guide to Deployment and Administration是一本关于ZooKeeper部署和管理的指南
BLOG域名:programb.blog.youkuaiyun.com
04-28 1963
它涵盖了部署系统的要求、支持的平台、所需的软件、集群设置、单服务器和开发人员设置，以及一些需要考虑的事项，如ZooKeeper的优点和局限性。总之，ZooKeeper管理员指南是一本全面而实用的参考书，对于需要部署和管理ZooKeeper的读者来说非常有价值。这包括如何识别和解决常见问题，如何设计和实施备份和恢复策略，以及如何利用ZooKeeper提供的各种工具进行故障排查。此外，该指南还提供了关于如何监控ZooKeeper的性能和可用性，以及如何处理故障转移和恢复的信息。
Servlet.service() for servlet [dispatcherServlet] in context with path []错误
麒麟臂刺啦的博客
11-14 2万+
做springboot项目对token认证时，在application.properties做了配置 token: tokenHeader: access-token tokenSecret: 86f3d82fed2348f49b38ec86c1f2fed2 @Data @Configuration @ConfigurationProperties(prefix = "token") public class TokenAuthenticationProperties { private
Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request p
weixin_45648976的博客
07-06 9552
控制台报错： Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is java.lang.NullPointerException] with root cause 项目启动运行后，控制台报了上面这个错误，意思是Servlet.service服务在路径为[diapatcherServlet]
报错Error resolving template template might not exist or might not be accessible解决方案
菜鸟要飞翔
01-04 3万+
根本的错误原因1：not exist 换句话说就是你给的路径找不到。 网上大致有这么两种解决方案： 查看你的@ResponseBody、@RestController用了没。 如果没加的话，只用@Controller默认的是你返回的是一个webapp(Resources同级文件夹)下的一个路径，而不是一个Json。这种情况的前提是是确实是一次ajax请求 关于返回路径前面的"/"。这个很明显，带...
【spring-boot】使用模板时出错：Error resolving template template might not exist or might not be accessible...
weixin_30498807的博客
08-06 800
解决：Error resolving template template might not exist or might not be accessible thymleaf模板的HTML文件必须是HTML5版本的文件，如果不是的话，那就从idea重新创建一个HTML5文件，然后将之前的文件内容拷贝一份到新创建的HTML5文件中。 转载于:https://www.cnbl...
解决Error resolving template template might not exist or might not be accessible问题
攻城狮不是猫
05-14 10万+
欢迎转载：攻城狮不是猫 thymeleaf + Spring Boot 在开发环境正常，但用jar运行时报错 Error resolving template template might not exist or might not be accessible; 这个问题我们都很好明白，就是模板页不存在，但是实际上它能找到模板页，但是在使用th:include标签的时候才会出错，这就是...
Servlet.service() for servlet [dispatcherServlet] in context with path []
刘贵庆的博客
04-21 1403
请看：(436条消息) JdbcTemplate空指针异常_刘贵庆的博客-优快云博客https://blog.csdn.net/xysxlgq/article/details/124323258
Error resolving template [user/all], template might not exist or might not be accessible by any of the configured Template Resolvers
09-01
"Error resolving template [user/all], template might not exist or might not be accessible by any of the configured Template Resolvers"这个错误信息的意思是，解析模板时发生了错误，并且可能是因为模板不存在或者无法被配置的模板解析器访问到。根据这个错误信息，可以推测出在解析名为"user/all"的模板时出现了问题，这个模板可能不存在或者无法被配置的模板解析器访问到。为了解决这个问题，可以尝试在项目的资源目录下添加相应的模板文件，并确保配置的模板解析器能够正确地访问到这个文件。<span class="em">1</span><span class="em">2</span><span class="em">3</span> #### 引用[.reference_title] - *1* *3* [Error resolving template [index], template might not exist or might not be accessible by any of the](https://blog.csdn.net/weixin_45790889/article/details/127026694)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_1"}}] [.reference_item style="max-width: 50%"] - *2* [解决Error resolving template [x] template might not exist or might not be accessible by any of the ...](https://blog.csdn.net/lvoelife/article/details/126450694)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_1"}}] [.reference_item style="max-width: 50%"] [ .reference_list ]
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值