The absolute uri: cannot be resolved in either web.xml or the jar files de

最新推荐文章于 2024-03-01 15:09:13 发布

爱看美剧真是太好了

最新推荐文章于 2024-03-01 15:09:13 发布

阅读量2.5k

点赞数 1

分类专栏：我的错就是你的错文章标签： web.xml resolved jarfiles

我的错就是你的错专栏收录该内容

65 篇文章

订阅专栏

本文介绍了一种常见的自定义JSP标签部署错误及其解决方案。错误表现为HTTP 500状态码，提示无法解析绝对URI。文章指出，将自定义的.tld文件放置在WEB-INF目录下可以有效解决问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

1 前言

特别蛋疼！！！就是上面问题，弄了一个晚上才解决。在 .jsp 引入了自己写的taglib 标签。然后一直报500。

HTTP Status 500 – Internal Server Error
Type Exception Report

Message The absolute uri: cannot be resolved in either web.xml or the jar files deployed with this application

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

org.apache.jasper.JasperException: The absolute uri:  cannot be resolved in either web.xml or the jar files deployed with this application
    org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:55)
    org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:293)
    org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:80)
    org.apache.jasper.compiler.TagLibraryInfoImpl.generateTldResourcePath(TagLibraryInfoImpl.java:251)
    org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:122)
    org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:434)
    org.apache.jasper.compiler.Parser.parseDirective(Parser.java:492)
    org.apache.jasper.compiler.Parser.parseElements(Parser.java:1448)
    org.apache.jasper.compiler.Parser.parse(Parser.java:145)
    org.apache.jasper.compiler.ParserController.doParse(ParserController.java:244)
    org.apache.jasper.compiler.ParserController.parse(ParserController.java:105)
    org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203)
    org.apache.jasper.compiler.Compiler.__compile(Compiler.java:374)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:351)
    org.apache.jasper.compiler.Compiler.compile(Compiler.java:335)
    org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:601)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:368)
    org.apache.jasper.servlet.JspServlet._serviceJspFile(JspServlet.java:385)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:742)
    org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
    org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:121)
    org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
Note The full stack trace of the root cause is available in the server logs.