WebLogic Exception error parsing descriptor in Web appplication Solution

Source: Internet
Author: User

If you use WebLogic to deploy a war project, some projects can be deployed, but some cannot. The following exception occurs.
The exception is as follows:
An error occurred during activation of changes, please see the log for details.
[Http: 101064] [webappmodule (oa_manager0: oa_manager0.3.war)] Error parsing descriptor in Web appplication "D:/09 projects/oa_manager0.3/oa_manager0.3.war" weblogic. application. moduleexception: unmarshaller failed at weblogic. servlet. internal. webappmodule. loaddescriptor (webappmodule. java: 758) at weblogic. servlet. internal. webappmodule. prepare (webappmodule. java: 260) at weblogic. application. internal. flow. modulelistenerinvoker. prepare (modulelistenerinvoker. java: 90) at weblogic. application. internal. flow. deploymentcallbackflow $1. next (deploymentcallbackflow. java: 318) at weblogic. application. utils. statemachinedriver. nextstate (statemachinedriver. java: 26) at weblogic. application. internal. flow. deploymentcallbackflow. prepare (deploymentcallbackflow. java: 53) at weblogic. application. internal. flow. deploymentcallbackflow. prepare (deploymentcallbackflow. java: 43) at weblogic. application. internal. basedeployment $1. next (basedeployment. java: 615) at weblogic. application. utils. statemachinedriver. nextstate (statemachinedriver. java: 26) at weblogic. application. internal. basedeployment. prepare (basedeployment. java: 236) at weblogic. application. internal. deploymentstatechecker. prepare (deploymentstatechecker. java: 147) at weblogic.deploy.internal.tar getserver. appcontainerinvoker. prepare (appcontainerinvoker. java: 61) at weblogic.deploy.internal.tar getserver. operations. activateoperation. createandpreparecontainer (activateoperation. java: 191) at weblogic.deploy.internal.tar getserver. operations. activateoperation. doprepare (activateoperation. java: 84) at weblogic.deploy.internal.tar getserver. operations. abstractoperation. prepare (abstractoperation. java: 197) at weblogic.deploy.internal.tar getserver. deploymentmanager. handledeploymentprepare (deploymentmanager. java: 724) at weblogic.deploy.internal.tar getserver. deploymentmanager. preparedeploymentlist (deploymentmanager. java: 1137) at weblogic.deploy.internal.tar getserver. deploymentmanager. handleprepare (deploymentmanager. java: 224) at weblogic.deploy.internal.tar getserver. deploymentservicedispatcher. prepare (deploymentservicedispatcher. java: 109) at weblogic.deploy.service.internal.tar getserver. deploymentreceivercallbackdeliverer. dopreparecallback (deploymentreceivercallbackdeliverer. java: 166) at weblogic.deploy.service.internal.tar getserver. deploymentreceivercallbackdeliverer. accesskey $100 (deploymentreceivercallbackdeliverer. java: 12) at weblogic.deploy.service.internal.tar getserver. deploymentreceivercallbackdeliverer $ 2.run( deploymentreceivercallbackdeliverer. java: 54) at weblogic. work. serverworkmanagerimpl $ workadapterimpl. run (serverworkmanagerimpl. java: 518) at weblogic.work.executethread.exe cute (executethread. java: 207) at weblogic. work. executethread. run (executethread. -Java: 179) caused by: COM. bea. XML. xmlexception: failed to load Java type corresponding to E = web-app @ http://java.sun.com/xml/ns/javaee at com. bea. staxb. runtime. internal. unmarshalresult. getpojobindingtype (unmarshalresult. java: 325) at com. bea. staxb. runtime. internal. unmarshalresult. determinetypeforglobalelement (unmarshalresult. java: 292) at com. bea. staxb. runtime. internal. unmarshalresult. determinetypeforglobalelement (unmarshalresult. java: 302) at com. bea. staxb. runtime. internal. unmarshalresult. determineroottype (unmarshalresult. java: 283) at com. bea. staxb. runtime. internal. unmarshalresult. unmarshaldocument (unmarshalresult. java: 153) at com. bea. staxb. runtime. internal. unmarshallerimpl. unmarshal (unmarshallerimpl. java: 65) at weblogic. descriptor. internal. marshallerfactory $1. createdescriptor (assumallerfactory. java: 138) at weblogic. descriptor. descriptormanager. createdescriptor (descriptormanager. java: 254) at weblogic. application. descriptor. abstractdescriptorloader. createdescriptor (abstractdescriptorloader. java: 359) at weblogic. application. descriptor. cachingdescriptorloader. supercreatedescriptor (cachingdescriptorloader. java: 166) at weblogic. application. descriptor. cachingdescriptorloader. access $000 (cachingdescriptorloader. java: 31) at weblogic. application. descriptor. cachingdescriptorloader $ iohelperimpl. parsexml (cachingdescriptorloader. java: 278) at weblogic. descriptor. descriptorcache. parsexml (descriptorcache. java: 324) at weblogic. application. descriptor. cachingdescriptorloader. createdescriptor (cachingdescriptorloader. java: 209) at weblogic. application. descriptor. abstractdescriptorloader. createdescriptor (abstractdescriptorloader. java: 328) at weblogic. application. descriptor. abstractdescriptorloader. getdescriptor (abstractdescriptorloader. java: 237) at weblogic. application. descriptor. abstractdescriptorloader. getrootdescriptorbean (abstractdescriptorloader. java: 217) at weblogic. servlet. internal. webappdescriptor. getwebappbean (webappdescriptor. java: 136) at weblogic. servlet. internal. webappmodule. loaddescriptor (webappmodule. java: 754 )... 24 more weblogic. application. moduleexception: unmarshaller failed
Failed to load Java type corresponding to E = web-app @ http://java.sun.com/xml/ns/javaee

 

Solution:

The problem occurs when the declaration part of the project's web. xml file turns out to be:

<Web-app version = "2.5"

Xmlns = "http://java.sun.com/xml/ns/javaee"

Xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"

Xsi: schemalocation = "http://java.sun.com/xml/ns/javaee

Http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd>

 

Changed:

<Web-app version = "2.4"

Xmlns = "http://java.sun.com/xml/ns/j2ee"

Xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"

Xsi: schemalocation = "http://java.sun.com/xml/ns/j2ee

Http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd>

The problem can be solved.

 

Cause analysis:

WebLogic does not support the J2EE 2.5 version. If you use the 2.5 version, a parsing error (as shown above) occurs. Change it to version 2.4.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.