Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-568

"jboss-deployment-structure.xml" with schema location fails to deploy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 1.0.0.Beta1
    • 1.0.0.Alpha19
    • Server
    • None

      A "jboss-deployment-structure.xml" with a schemaLocation attribute will fail to deploy.

      This is a sample file:
      <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="urn:jboss:deployment-structure:1.1 http://www.jboss.org/schema/jbossas/jboss-deployment-structure-1_1.xsd">

      ...
      </jboss-deployment-structure>

      And this is the deployment error:
      And this is the parse exception:

      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,129]
      Message: JBAS018754: Unexpected content of type 'element start', name is '

      {urn:jboss:deployment-structure:1.1}

      jboss-deployment-structure', text is: 'null'
      at org.jboss.as.server.deployment.module.descriptor.JBossDeploymentStructureParser11.unexpectedContent(JBossDeploymentStructureParser11.java:1129) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
      at org.jboss.as.server.deployment.module.descriptor.JBossDeploymentStructureParser11.readElement(JBossDeploymentStructureParser11.java:211) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
      at org.jboss.as.server.deployment.module.descriptor.JBossDeploymentStructureParser11.readElement(JBossDeploymentStructureParser11.java:69) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
      at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
      at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
      at org.jboss.as.server.deployment.module.descriptor.DeploymentStructureDescriptorParser.parse(DeploymentStructureDescriptorParser.java:316) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
      ... 8 more

      The schemaLocation attribute makes sense, because Eclipse will be able to validate the file,and you have code completion. With the JBossTools plugin, the "xmlns" attribute is enough to get all this, because JBossTools adds this file to the xml catalog.

              sdouglas1@redhat.com Stuart Douglas (Inactive)
              wolfgangknauf Wolfgang Knauf
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: