Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-15181

Invalid content error when creating a seam project with EAP 6

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • 4.1.0.CR1
    • 4.1.0.CR1
    • seam2
    • None
    • Hide

      1. Have JBDS with EAP 6.1 server - e.g. install JBDS with the embedded EAP 6.1
      2. Add EAP 6.0.1 server
      3. Add Seam 2.3.1 runtime
      4. Create a Seam Web Project
      5. Check the error log or see the error icon in the project explorer

      Show
      1. Have JBDS with EAP 6.1 server - e.g. install JBDS with the embedded EAP 6.1 2. Add EAP 6.0.1 server 3. Add Seam 2.3.1 runtime 4. Create a Seam Web Project 5. Check the error log or see the error icon in the project explorer

      While verifying JBIDE-13965 I encountered this problem:
      When you create a seam project, there is an error in jboss-deployment-structure.xml:

      cvc-complex-type.2.4.a: Invalid content was found starting with element 
       'deployment'. One of '{ear-subdeployments-isolated, deployment, sub-deployment, 
       module}' is expected.
      

      The content of the file is as follows:

      <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">
        <deployment>
        	  <dependencies>
      	      <module name="org.hibernate" export="true"/>
      	      <module name="javax.faces.api" export="true" />
                <module name="com.sun.jsf-impl" export="true"/>
                <module name="org.dom4j" export="true"/>
                <module name="org.hibernate.validator" export="true"/>
      	    </dependencies>
        </deployment>  
      </jboss-deployment-structure> 
      

      Note that the seam project still deploys fine on the server.
      Also, there is no such error with EAP 5.x.

              alexeykazakov Alexey Kazakov
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: