cvc-complex-type.2.4.a: Invalid content was found starting with element 'async-supported'. One of '{"http://java.sun.com/xml/ns/javae
第一種方案: 將 "http://java.sun.com/xml/ns/javaee" 換為 "http://java.sun.com/xml/ns/j2ee"
錯誤,錯誤原因為 根元素<web-app>中的模式檔案不對,javaee只支援單個的config,要換成 j2ee 經過測試,修改完還會報錯。
第二種方案:直接將 xmlns="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" 刪除(或註釋)
經測試,不再報錯
相關推薦
cvc-complex-type.2.4.a: Invalid content was found starting with element
lex -s 2.4 logs nbsp onf -type sch xsd cvc-complex-type.2.4.a: Invalid content was found starting with element ‘display-name‘. One of ‘{
web.xml 中async-supported爆紅叉叉 cvc-complex-type.2.4.a: Invalid content was found starting with element 39;async-supported39;.
class 表頭 start lex .org nco app lns pri 新建一個項目在web.xml中些東西是發現async-supported報紅叉 cvc-complex-type.2.4.a: Invalid content was found starti
轉:web.xml檔案報錯:cvc-complex-type.2.4.a: Invalid content was found starting with element 39;init-param39;.
<?xml version="1.0" encoding="UTF-8"?> <web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns
cvc-complex-type.2.4.a: Invalid content was found starting with element 39;async-supported39;. One of 39;{"http://java.sun.com/xml/ns/javae
第一種方案: 將 "http://java.sun.com/xml/ns/javaee" 換為 "http://java.sun.com/xml/ns/j2ee"  
cvc-complex-type.2.4.a: Invalid content was found starting with element 39;servlet-pattern39;. One of
報錯提示是:cvc-complex-type.2.4.a: Invalid content was found starting with element 'servlet-pattern'. One of '{"http://java.sun.com/xml/ns/java
cvc-complex-type.2.4.a: Invalid content was found starting with element 39;executable39;.
maven工程中的pom.xml報錯: cvc-complex-type.2.4.a: Invalid content was found starting with element 'executable'. One of '{"http://maven.apache.org/POM/4.0.
在eclipse中web.xml報錯:cvc-complex-type.2.4.a: Invalid content was found starting with element 'async-su
在eclipse中web.xml報錯:cvc-complex-type.2.4.a: Invalid content was found starting with element ‘async-supported’ 在配置web.xml的時候出現cvc-com
cvc-complex-type.2.4.a: Invalid content was found starting with element 'taglib'錯誤
今天在使用struts-menu製作選單,在web.xml中寫入 <taglib> <taglib-uri>/WEB-INF/struts-menu.tld</taglib-uri> <taglib-locati
cvc-complex-type.2.4.a: Invalid content was found starting with element 'attribute'. One of '{"http:
tld檔案中<attribute></attribute>標籤提示如下: cvc-complex-type.2.4.a: Invalid content was found starting with element 'query'. One of
針對報出 cvc-complex-type.2.4.a: Invalid content was found starting with element 問題解決辦法
今天正在整java專案時突然在web.xml報出cvc-complex-type.2.4.a: Invalid content was found starting with
關於配置攔截器報錯:cvc-complex-type.2.4.a: Invalid content was found starting with element
解決辦法為:將“http://www.springmodules.org/schema/cache/springmodules-cache.xsd http://www.springmodules.org/schema/cache/springmodules-ehcache.
cvc-complex-type.2.4.a: Invalid content was found starting with element 'url-pattern'
以前用myeclipse嫌validate太煩了就都去掉了,把專案匯入到Eclipse中,發現回報各種validate錯誤,如題在web.xml檔案報錯,以前沒發現,從字面意思理解就是‘url-pattern’ 元素在2.4的版本里無效換成2.5試試,注意下面程式碼紅色部分
taglib cvc-complex-type.2.4.a: Invalid content was found starting with element 'taglib'.
web.xml標籤中的taglib標籤出錯,顯示cvc-complex-type.2.4.a: Invalid content was found starting with element 'taglib' 解決辦法是:在標頭檔案的 xmlns:xsi="http://w
cvc-complex-type.2.4.d: invalid content was found starting with element
web.xml裡面一直畫紅,是因為以前寫成 <filter> <filter-name>hibernateFilter</filter-name> <
Invalid content was found starting with element No child ele
分享一下我老師大神的人工智慧教程!零基礎,通俗易懂!http://blog.csdn.net/jiangjunshow 也歡迎大家轉載本篇文章。分享知識,造福人民,實現我們中華民族偉大復興!  
spring Invalid content was found starting with element 'init- param'
初學spring,配置web.xml,發現報個錯,莫名其妙的。 錯誤資訊如下 自己幹看是不知道咋回事。 後來上網百度,發現是程式碼順序錯誤,load-on-startup應該放到init-param下面,額。 so,改動下,沒事了。
啟動weblogic報錯:string value 39;2.439; is not a valid enumeration value for web-app-versionType in namespace http://java.sun.com/xml/ns/javaee
-a xsd not app b- 1.0 ring encoding ont 啟動報錯: 原因:有人改動了web.xml的頭 解決方法: 在web.xml中修改擡頭為: <?xml version="1.0" encoding="UTF-8"?> <we
Type cvc-complex-type.2.4.c: The matching wildcard is strict...
nco odin context blog ring color 報錯 log 記錄 這個問題困擾了我兩次,分別說一下原因:1. 如網上一些網友所言,是在配置Spring的標簽庫的時候有拼寫錯誤或者遺漏。下面貼一個標準3.0的吧: 1 <?xml version=
[bug]cxf: cvc-complex-type.2.4.c: 通配符的匹配很全面, 但無法找到元素 39; 39;jaxws:server39; 的聲明,問題處理
alt 運行 提示頁面 題解 src 配置信息 圖片 image 原因 問題原因: 未知,因個人環境不同,無法保證都適用 問題解決方法: 將cxf在spring的配置信息調整到最前方 原配置信息頭: 運行時錯誤提示: 調
《Spring實戰》-- 39;cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element39; 錯誤的解決
tip c-c 面向切面 ng- join proc ima -a edi 在Eclipse中新建了一個maven項目學習Spring,在 service.xml 中配置 Spring,想要學習‘面向切面的Spring’,service.xml 內容如下: <bean