XML : javax.xml.stream.XMLStreamException: ParseError at [row,col]:[11,3] in jboss-web.xml

I am using java 1.6 , jboss 6.1. My application is running on jboss 5.1 but When am I trying to run my application on jboos 6.1 I get the bellow error.

javax.xml.stream.XMLStreamException: ParseError at [row,col]:[11,3] in jboss-web.xml

jboss Log.

  00:06:52,823 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "MyApplication-0.0.1-SNAPSHOT.war" (runtime-name: "MyApplication-0.0.1-SNAPSHOT.war")  00:06:54,743 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."MyApplication-0.0.1-SNAPSHOT.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."MyApplication-0.0.1-SNAPSHOT.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "MyApplication-0.0.1-SNAPSHOT.war"           Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor "/content/MyApplication-0.0.1-SNAPSHOT.war/WEB-INF/jboss-web.xml" at [11,3]          at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:79)          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]          ... 5 more  Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[11,3]  Message: Unexpected element 'class-loading' encountered          at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109)          at org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:206)          at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:71)          ... 6 more    00:06:54,748 ERROR [org.jboss.as.server] (HttpManagementService-threads - 8) JBAS015870: Deploy of deployment "MyApplication-0.0.1-SNAPSHOT.war" was rolled back with the following failure message:   {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"MyApplication-0.0.1-SNAPSHOT.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"MyApplication-0.0.1-SNAPSHOT.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"MyApplication-0.0.1-SNAPSHOT.war\"      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor \"/content/MyApplication-0.0.1-SNAPSHOT.war/WEB-INF/jboss-web.xml\" at [11,3]      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[11,3]  Message: Unexpected element 'class-loading' encountered"}}  00:06:54,867 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment MyApplication-0.0.1-SNAPSHOT.war (runtime-name: MyApplication-0.0.1-SNAPSHOT.war) in 118ms  

This is the file where I am getting exception jboss-web.xml

  <?xml version="1.0" encoding="UTF-8"?>  <jboss-web>            <!--   <context-root>MyApplication</context-root>    <class-loading java2ClassLoadingCompliance="false">    <loader-repository>com.globalss:loader=MyApplication.war    <loader-repository-config>java2ParentDelegation=false</loader-repository-config>    </loader-repository>     </class-loading>-->        <class-loading java2ClassLoadingCompliance="false">    <loader-repository>         org.myapp:loader=MyApplication.war        <loader-repository-config>java2ParentDelegation=false        </loader-repository-config>     </loader-repository>   </class-loading>          <resource-ref>                  <res-ref-name>database</res-ref-name>                  <jndi-name>java:/database</jndi-name>          </resource-ref>          <resource-ref>                  <res-ref-name>dataSource</res-ref-name>                  <jndi-name>java:/dataSource</jndi-name>          </resource-ref>  </jboss-web>  

Why do we get this error?

What is the root cause of getting this error?

How do we solve this error?

No comments:

Post a Comment