[jbosstools-issues] [JBoss JIRA] (JBIDE-14534) Errors in Spring project archetypes

[Joshua Wilson (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-14534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12826388#comment-12826388 ] 

Joshua Wilson commented on JBIDE-14534:
---------------------------------------

Regarding how changing the version makes the error go away in Eclipse. While this is true it does not actually allow you to deploy the application to JBoss (where the schema lives).

After looking deeper into this I believe that they are right on  JBIDE-14629, and that the elementFormDefault="unqualified" needs to be changed to elementFormDefault="qualified".
                
> Errors in Spring project archetypes
> -----------------------------------
>
>                 Key: JBIDE-14534
>                 URL: https://issues.jboss.org/browse/JBIDE-14534
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central, project-examples, upstream
>    Affects Versions: 4.1.0.Beta1
>         Environment: JBT 4.1.0.Beta1
>            Reporter: Radim Hopp
>            Assignee: Snjezana Peco
>             Fix For: 4.1.x
>
>
> There are 2 errors in Spring Project archetype:
> {code}
> Description	Resource	Path	Location	Type
> 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.	jboss-deployment-structure.xml	/jboss-springmvc-webapp/src/main/webapp/WEB-INF	line 2	XML Problem
> 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.	jboss-deployment-structure.xml	/jboss-springmvc-webapp/src/main/webapp/WEB-INF	line 2	XML Problem
> {code}
> [0] https://bugzilla.redhat.com/show_bug.cgi?id=996680
> [1] https://issues.jboss.org/browse/WFLY-943

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira