metadata-complete="true"

最新推荐文章于 2023-07-06 00:02:58 发布
最新推荐文章于 2023-07-06 00:02:58 发布
阅读量2.1k 收藏 1
点赞数
本文记录了一次在启动Tomcat时遇到的警告信息，并详细解释了如何通过调整web.xml配置文件来解决这些问题。作者在引入额外的jar包后遇到了无法加载特定类的警告，最终通过设置metadata-complete属性为true解决了这一难题。

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

信息: validateJarFile(D:\Program Files\WorkspaceShiro\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\shirodemo\WEB-INF\lib\javax.servlet-api-3.1.0.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
七月 26, 2017 10:03:48 下午 org.apache.catalina.startup.ContextConfig checkHandlesTypes
警告: Unable to load class [javax.servlet.http.HttpSessionIdListener] to check against the @HandlesTypes annotation of one or more ServletContentInitializers. 
java.lang.ClassNotFoundException: javax.servlet.http.HttpSessionIdListener
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1666)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1511)
at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:1883)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:1846)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1733)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1692)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1678)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1245)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:313)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:89)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4667)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:771)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:275)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:427)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:649)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.startup.Catalina.start(Catalina.java:585)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:415)


七月 26, 2017 10:03:48 下午 org.apache.catalina.startup.ContextConfig checkHandlesTypes
警告: Unable to load class [javax.servlet.http.HttpUpgradeHandler] to check against the @HandlesTypes annotation of one or more ServletContentInitializers. 
java.lang.ClassNotFoundException: javax.servlet.http.HttpUpgradeHandler
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1666)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1511)
at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:1883)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:1846)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1733)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1692)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1678)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1245)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:313)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:89)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4667)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:771)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:275)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:427)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:649)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.startup.Catalina.start(Catalina.java:585)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:415)


七月 26, 2017 10:03:48 下午 org.apache.catalina.startup.ContextConfig checkHandlesTypes
警告: Unable to load class [javax.servlet.http.WebConnection] to check against the @HandlesTypes annotation of one or more ServletContentInitializers. 
java.lang.ClassNotFoundException: javax.servlet.http.WebConnection
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1666)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1511)
at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:1883)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:1846)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1733)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1692)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1678)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1245)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:313)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:89)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4667)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:771)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:275)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:427)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:649)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.startup.Catalina.start(Catalina.java:585)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:415)


七月 26, 2017 10:03:48 下午 org.apache.catalina.startup.ContextConfig checkHandlesTypes
警告: Unable to load class [javax.servlet.ReadListener] to check against the @HandlesTypes annotation of one or more ServletContentInitializers. 
java.lang.ClassNotFoundException: javax.servlet.ReadListener
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1666)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1511)
at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:1883)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:1846)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1733)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1692)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1678)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1245)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:313)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:89)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4667)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:771)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:275)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:427)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:649)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.startup.Catalina.start(Catalina.java:585)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:415)


七月 26, 2017 10:03:48 下午 org.apache.catalina.startup.ContextConfig checkHandlesTypes
警告: Unable to load class [javax.servlet.WriteListener] to check against the @HandlesTypes annotation of one or more ServletContentInitializers. 
java.lang.ClassNotFoundException: javax.servlet.WriteListener
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1666)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1511)
at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:1883)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:1846)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1733)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1692)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1678)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1245)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:313)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:89)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4667)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:771)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:988)
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:275)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:427)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:649)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
at org.apache.catalina.startup.Catalina.start(Catalina.java:585)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:415)



上网各种查啊，有的说少包的，有的说包可能重复有冲突的......

我用的rest框架，需要的包一个不多一个不少，也是从上一个项目中考过来的。现在可以启动tomcat服务，也没有错误。

但是我还需要引用公司内部几个jar包，问题就来了上面所报的错。

后来我改了下web.XML配置文件

<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" id="WebApp_ID" version="3.0" metadata-complete="true" >

在里面添加了metadata-complete="true" ok了。


甘韦
关注
8K HDR!｜为 Chromium 实现 HEVC 硬解 - 原理/实测指南
字节跳动视频云
07-13 6710
如果有 HEVC 视频播放需求，不妨可以尝试一下 Chrome Canary 版本或预编译版本。
5-1 Velero 备份 Kubernetes 详解
qq_25874461的博客
03-12 469
详细介绍 Velero 工具的原理和使用方法，并备份单个 namespace 示例
web.xml metadata-complete="true"
金溪的博客
05-25 3594
web.xml文件中使用元素通知Web容器是否要寻找注解，如果你将设为false，或者在文件中不指定元素，那么在部署期间，容器必须扫描注解和Web分片，为Web应用程序构建有效的元数据。如果将设为true，将由部署描述符为Web应用程序提供所有的配置信息   最后欢迎大家访问我的个人网站：1024s...
metadata-complete讲解
chuixue24的博客
12-09 1708
在web应用中，使用注解的类仅当它们位于WEB-INF/classes目录中，或它们被打包到位于应用的WEB-INF/lib中的jar文件中时它们的注解才将被处理。 Web应用部署描述符的web-app元素包含一个新的“metadata-complete”属性。“metadata-complete”属性定义了web描述符是否是完整的，“metadata-complete”设置为“true”表示...
【已解决】IDEA启动tomcat时,所有的servlet文件不可访问,但Tomcat配置没有问题，是web.xml配置出错。metadata-complete=“true“
qq_57145497的博客
07-06 1743
IDEA启动Tomcat时，所有的servlet文件不可访问，但是静态资源访问正常，Tomcat配置没有问题，web.xml配置出错，需要将metadata-complete设置为false，或者不设该属性。
web配置文件属性metadata-complete讲解
chuidanjie3550的博客
07-10 361
metadata-complete属性的作用 在启动@webservlet注解的时候，需要配合web.xml配置文件属性才能生效，否则容易报如下访问错误： 需要将metadata-complete设置为false，或者不设该属性。 metadata-complete属性讲解 S...
<?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" version="3.1" metadata-complete="true"> <display-name>Welcome to Tomcat</display-name> <description> Welcome to Tomcat </description> </web-app>
最新发布
08-12
注意：用户提供的web.xml内容中，metadata-complete="true"表示该web.xml是完整的，不会扫描注解（即不会处理Servlet注解等）。 步骤： 1. 安装Tomcat 8.5（简要说明，因为之前已经详细说明过）。 2. 查看默认...
kubectl命令使用
yanghx2的博客
12-20 3087
kubectl命令使用 create kubectl create deployment NAME --image=image -- [COMMAND] [args...] //格式 [root@master ~]# kubectl create deployment test1 --image busybox deployment.apps/test1 created //使用busybox镜像创建一个test1的pod [root@master ~]# kubectl get pod NAME
[root@ml-master ~]# sudo yum update -y --nogpgcheck ca-certificates nss Loaded plugins: fastestmirror, : langpacks Loading mirror speeds from cached hostfile Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error" One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7/x86_64 [root@ml-master ~]#
06-11
Metadata cache created. openssl.x86_64 1:1.0.2k-26.el7_9.1 updates 1.5 MB Complete! ``` ### 验证步骤 ```bash # 验证SSL连接 openssl s_client -connect mirrors.aliyun.com:443 # 验证镜像源 curl -I ...
tomcat WebXml类的metadataComplete属性值
weixin_36677876的博客
03-11 544
在servlet3.0以后,我们想要定义一个Servlet可以不再使用web.xml,可以直接在Servlet类上加@WebServlet注解来代替在web.xml配置一堆 但是WebXml类有一个属性,metaDataComplete 默认值是false 当其变为true后,前面说的直接在Servlet类上加@WebServlet注解就失效了 其在web.xml中的定义如上图所示 在ContextConfig类中,要不要去扫描加了@WebServlet注解的类逻辑代码如下 ...
servlet3.X中的metadata-complete属性
冲吧，不要停！
11-01 6656
http://www.copperykeenclaws.com/tomcat-and-servlet-3-0-web-configuration/ 在Servlet3.X的web.xml中可以设置metadata-complete属性，例如： web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="h
Web开发 web.xml中metadata-complete属性
猫君之上的博客
02-23 5808
无论是Servlet，还是Filter，Listener等，在自定义Filter时，要想使它起作用，那么必须要对它进行配置，一般都有两种配置的方式,一种是基于``配置式的，另一种则是基于注解式`的。 以Servlet为例： 在web.xml中配置： &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt; &amp;lt;web-app xmln
小结web.xml文件之metadata-complete
cmolong的博客
02-14 1951
metadata-complete： &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;属性值：&nbsp;&nbsp;&nbsp;&nbsp;true&nbsp;&nbsp;&nbsp;&nbsp;flase &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&am
web.xml文件中metadata-complete标签简解
王永川的专属博客
05-07 1847
1. 如果当前项目有使用annotation声明的servlet或者filter,那么metadata-complete需要声明为false ，不写默认false 2.  metadata-complete=true时,容器只会扫描当前文件中的配置,不再扫描文件所在jar中声明的配置 ...
servlet3.0，web.xml的metadata-complete的作用
deke3032的博客
10-09 234
　　metadata-complete是servlet3.0规范中的新增的属性,该属性接受两个属性值，true或false。当该属性值为true时，该web应用将不会加载Annotation配置的web组件（如servlet、Filter、Listener等）。 转载于:https://www.cnblogs.com/hongcong/p/5942120.html...
metadata-complete 造成servlet无法通过注解访问
weixin_45500051的博客
07-31 477
晚上在练习代码的时候,发现无法通过注解去访问到servlet文件, 找了很久才知道是因为 web.xml里面的metadata-complete 属性设置成了true. metadata-complete 属性如果为true , 那么部署项目的时候 ,访问的路径就只能依赖于 xml文件的方式 ,而不能通过注解进行访问到. 特此记录 ...
springmvc spring mybatis 整合
LaoLi07的博客
10-15 715
在这个文档中只会有错误或者是解答 一、Web程序加载时错误 1.1、java.lang.reflect.InvocationTargetException   =====在web.xml中的web-app中加入： metadata-complete="true" 网页上的解释： web.xml文件中使用元素通知Web容器是否要寻找注解，如果你将设为false，或者在文件
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值