处理异常Error resolving template [/login], template might not exist or might not be accessible by......

最新推荐文章于 2024-03-16 22:39:12 发布
最新推荐文章于 2024-03-16 22:39:12 发布
阅读量1.8k 收藏
点赞数
文章标签： 网络 ldap webpack ViewUI
原文链接：http://www.cnblogs.com/songzehao/p/10854256.html
版权

项目开发环境：Eclipse+SpringBoot+thymeleaf

本地开发测试都是在Eclipse中Run或Debug，页面都能正常访问；

使用Maven打成jar包，准备上线部署，java -jar命令启动服务，报错找不到template模板页面[/login]：

2019-04-30 17:10:44  [ http-nio-7070-exec-1:288156 ] - [ ERROR ]  [THYMELEAF][http-nio-7070-exec-1] Exception processing template "/login": Error resolving template [/login], template might not exist or might not be accessible by any of the configured Template Resolvers
org.thymeleaf.exceptions.TemplateInputException: Error resolving template [/login], 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)
	at org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:607)
	at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1098)
	at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1072)
	at org.thymeleaf.spring5.view.ThymeleafView.renderFragment(ThymeleafView.java:362)
	at org.thymeleaf.spring5.view.ThymeleafView.render(ThymeleafView.java:189)
	at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1370)
	at org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1116)
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1055)
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:942)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1005)
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:897)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:634)
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:882)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:99)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:92)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.springframework.web.filter.HiddenHttpMethodFilter.doFilterInternal(HiddenHttpMethodFilter.java:93)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:200)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:200)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:834)
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1415)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:748)

难道Maven打包出错，把template下的页面文件都没打进去？打开jar包，页面文件都在，没什么异常的地方。

那为何一部署就找不到[/login]这个页面呢？看看Java代码：

@GetMapping("/login")
public String login() {
	return "/login";
}

解决这个错误需要将“/”去掉，即：

@GetMapping("/login")
public String login() {
	return "login";
}

 

转载于:https://www.cnblogs.com/songzehao/p/10854256.html

weixin_34323858
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
解决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
SpringBoot项目打包jar后运行报错Error resolving templ ate [XXX], template might not exist
云泽的博客
07-26 1440
SpringBoot项目在IDEA开发期间运行一切正常，但是打成jar包后运行出现页面访问不了，报如下错误： 2020/07/26-20:42:41 [http-nio-8081-exec-3] ERROR org.thymeleaf.TemplateEngine- [THYMELEAF][http-nio-8081-exec-3] Exception processing template “/i18n/before”: Error resolving templ ate [/i18n/before],
The Open Group Base Specifications Issue 6 IEEE Std 1003.1, 2004 Edition
04-28
The 2004 edition incorporates Technical Corrigendum Number 1 and Technical Corrigendum 2 addressing problems discovered since the approval of the 2001 edition. These are mainly due to resolving integration issues raised by the merger of the Base documents.
踩坑，Error resolving template [index], template might not exist or might not be accessible by any
最新发布
qq_43406318的博客
03-16 660
解决：org.thymeleaf.exceptions.TemplateInputException: Error resolving template [index], template might not exist or might not be accessible by any of the configured Template Resolvers。在springboot整合thymeleaf，遇到错误：模板可能不存在或无法被任何配置的模板解析器访问。解决方法：在pom.xml添加。
Article_Src.zip_.src.zi_DNS Csharp_Everything and More_dns resol
09-24
The main core of DNS resolving is the resolver . This class wraps queries into DNS packets and sends them to any DNS server. The response is then decoded into some useful information (at least for programmers, or for me in special -)). All my DNS stuff uses the namespace Heijden.DNS. Don t change it in your applications, it gives me some comfort knowing my name is stored in some nice other projects. Don t forget to let me know. Because I don t want to go immediately into details in this article, I only show the usage of the resolver component to warm you up. As the best way to do this, I have built a Dig class which acts like the good-old-Unix-style dig. Its acts like dig, but it is not a complete dig implementation. It does, however, do everything you want it to, presenting the output in more or less the same format. This is the outline of the Dig class:
Node.js in Practice_1st Edition
04-19
英文原版，无水印，数字版，有目录。 Node.js in Practice 1st Edition Summary Node.js in Practice is a collection of fully tested examples that offer solutions to the common and not-so-common issues you face when you roll out Node. You'll dig into important topics like the ins and outs of event-based programming, how and why to use closures, how to structure applications to take advantage of end-to-end JavaScript apps, and more. Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications. About the Book You've decided to use Node.js for your next project and you need the skills to implement Node in production. It would be great to have Node experts Alex Young and Marc Harter at your side to help you tackle those day-to-day challenges. With this book, you can! Node.js in Practice is a collection of 115 thoroughly tested examples and instantly useful techniques guaranteed to make any Node application go more smoothly. Following a common-sense Problem/Solution format, these experience-fueled techniques cover important topics like event-based programming, streams, integrating external applications, and deployment. The abundantly annotated code makes the examples easy to follow, and techniques are organized into logical clusters, so it's a snap to find what you're looking for. Written for readers who have a practical knowledge of JavaScript and the basics of Node.js. What's Inside Common usage examples, from basic to advanced Designing and writing modules Testing and debugging Node apps Integrating Node into existing systems About the Authors Alex Young is a seasoned JavaScript developer who blogs regularly at DailyJS. Marc Harter works daily on large-scale projects including high-availability real-time applications, streaming interfaces, and other data-intensive systems. Table of Contents PART 1 NODE FUNDAMENTALS Getting started Globals: Node's environment Buffers: Working with bits, bytes, and encodings Events: Mastering EventEmitter and beyond Streams: Node's most powerful and misunderstood feature File system: Synchronous and asynchronous approaches Networking: Node's true "Hello, World" Child processes: Integrating external applications with Node PART 2 REAL-WORLD RECIPES The Web: Build leaner and meaner web applications Tests: The key to confident code Debugging: Designing for introspection and resolving issues Node in production: Deploying applications safely PART 3 WRITING MODULES Writing modules: Mastering what Node is all about
Error resolving template [login], template might not exist or might not be accessible by any of 问题
你好_晴天
10-21 5198
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 6764
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"; } 解决方法： 找一下配置
Error resolving template [], template might not exist or might not be accessible by any of the conf
热门推荐
圆号本号
04-06 2万+
一、问题： Error resolving template [/index], template might not exist or might not be accessible by any of the configured Template Resolvers 出现在 SpringBoot 项目使用 java -jar 运行时 二、解决 分别检查下面三个地方 2.1 在 pom.xml 中添加 thymeleaf 依赖 没有的话加下，有的话不用加 <dependency>
Springboot返回页面出现Error resolving template [login.html] 的报错处理
weixin_43829645的博客
04-09 1万+
今天使用Springboot集成thymeleaf返回页面时的结果一不小心出现了 Error resolving template [login.html], template might not exist or might not be accessible by any of the configured Template Resolvers这个错误，最后瞄瞄发现是一个常识性的错误，就结合其...
warning ..\package.json: No license field
01-07
在初始化Vue项目的的时候发现警告 yarn install 查了下发现是，package.json 文件中缺少license参数 { name: movie_view, version: 0.1.0, license: MIT, private: true, scripts: { serve: vue-cli-service serve, build: vue-cli-service build, lint: vue-cli-service lint }, dependenci
vue-admin-template-4.4.0.zip
03-01
vue-admin-template-4.4.0.zip
Exception evaluating SpringEL expression: “session.user.name“ (template: “system/index/index“ - lin
jq1223的博客
01-20 4240
his application has no explicit mapping for /error, so you are seeing this as a fallback. Tue Jan 19 22:52:21 CST 2021 There was an unexpected error (type=Internal Server Error, status=500). An error happened during template parsing (template: "class path
Exception processing template “user/login“: Error resolving template [user/login], template might no
weixin_52695807的博客
08-16 528
通常，您可以在@RestController方法中直接返回数据对象，框架将自动将其转换为适当的数据格式（例如JSON）并将其发送给客户端。@Controller注解用于创建一个标准的MVC（Model-View-Controller）控制器，它可以处理HTTP请求并返回相应的视图。通常，您可以在@Controller方法中使用ModelAndView对象来处理请求并返回视图名称，然后框架将根据视图名称解析并呈现相应的视图。它们之间的主要区别在于返回值的处理方式。
Error resolving template [swagger-ui.html], template might not exist or might not be accessible by a
riemann_的博客
12-18 2928
2019-12-18 20:03:59:278 ERROR [http-nio-8080-exec-1] o.a.c.c.C.[.[localhost].[/].[dispatcherServlet]-175 Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Requ...
处理异常Error resolving template [/login], template might not exist or might not be accessible by......
我惠依旧的博客
03-03 4079
原文地址 项目开发环境：Eclipse+SpringBoot+thymeleaf 本地开发测试都是在Eclipse中Run或Debug，页面都能正常访问； 使用Maven打成jar包，准备上线部署，java -jar命令启动服务，报错找不到template模板页面[/login]： 2019-04-30 17:10:44 [ http-nio-7070-exec-1:288156 ] ...
Error resolving template [index], template might not exist or might not be accessible by any of the
weixin_62948669的博客
09-26 1611
报错的意思是说解析模板[index]出错，模板可能不存在或无法被任何配置的模板解析器访问。这样再运行项目就没没问题了，真的是小小的细节就会导致项目运行不起来。然后我找了很久我以为是pom文件的事，后来看了看配置类。就因为一个/然后这个没解析到。
Error resolving template [login.html], template might not exist or might not be accessible by any of the configured Template Resolvers
03-16
这个错误提示是在使用模板引擎时出现的，它表示无法解析模板[login.html]，可能是因为该模板不存在或者无法被配置的模板解析器访问到。 模板引擎是一种将数据和模板结合生成最终输出的工具。在使用模板引擎时，我们需要配置一个或多个模板解析器来解析和加载模板文件。当模板引擎无法找到或访问到指定的模板文件时，就会出现这个错误。 要解决这个问题，你可以按照以下步骤进行排查： 1. 确认模板文件是否存在：检查模板文件[login.html]是否存在于指定的路径中。确保文件名和路径都是正确的。 2. 检查模板解析器配置：确认你的模板解析器是否正确配置，并且能够访问到模板文件所在的路径。检查配置文件或代码中的相关配置项，确保路径设置正确。 3. 检查权限设置：如果模板文件所在的路径有权限限制，确保你的应用程序有足够的权限来读取该文件。可以尝试修改文件权限或者将文件移动到应用程序可以访问的路径下。 4. 检查模板文件格式：如果模板文件存在但仍然无法解析，可能是因为文件格式有误。确保模板文件的语法和格式正确，没有语法错误或其他问题。

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值