On 11 Apr 2016, at 9:15, Marek Novotny wrote:
Isn't JBoss AS 7.x compliant to Java EE 6 specs which is the XSD
there referenced/imported from Sun?
I guess you mixed Java EE 6 with JBoss AS 7 versions here.
Rob - is the error you see on the jboss-application.xml you wrote or in
the included xsd ?
What 7.0 are you trying to set/add ?
On 8.4.2016 15:35, Rob Stryker wrote:
> While investigating a jira
> I tried to make a minimalist jboss-application xml, and it had a
> strange validation error:
> cvc-complex-type.3.1: Value '7.0' of attribute 'version' of element
> 'jboss-app' is not valid with respect to the corresponding attribute
> use. Attribute 'version' has a fixed value of '6'.
> When I dug into the current jboss-app_7_0.xsd to see what was going
> I saw the following:
> <!-- Import the Java EE6 xsd -->
> <xs:import namespace="http://java.sun.com/xml/ns/javaee"
> <!-- Include the common JBoss EE elements -->
> <xs:include schemaLocation="jboss-common_6_0.xsd"/>
> Shouldn't this be pulling from application_7.xsd at least? Also we
> don't seem to have a jboss-common_7_0.xsd. So these version
> inconsistancies are really angering the eclipse validator.
> Is there anything that can be done here at all? It really seems our
> schema have this recurring problem of not validating in eclipse, and
> often times it seems the problems lead back to our very own schema as
> the cause. It ends up causing errors in eclipse and our users get
> confused why all our example projects or snippets of xml on redhat
> access often fail to validate.
> - Rob Stryker
> wildfly-dev mailing list
Windup team member and Seam Project Lead
Red Hat Czech s.r.o.
612 45 Brno
wildfly-dev mailing list