[jboss-jira] [JBoss JIRA] (WFLY-2480) Investigate Infinispan test XML files do not validate against XSD yet are parsed ok

[Radoslav Husar (JIRA)]

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

Radoslav Husar edited comment on WFLY-2480 at 2/20/15 12:09 PM:
----------------------------------------------------------------

So this is a couple of issues together. They mostly come from the restrictions of XSD and its state machine..

{quote} The type has an 'all' model group in its \{content type\} and thus cannot be derived from a non-empty type, since this would produce a 'sequence' model group containing the 'all' model group; 'all' model groups are not allowed to appear inside other model groups.{quote}

In short, the order needs to be forced (sequence) if we want to continue using derived/extended types.

So fixing ordering discrepancy between XSD and Writer:
* state transfer in writer and test files
* binary/string-keyed-table in xsd

and
* backup-for/backups XSD discrepancy: both can be actually used simultaneously

...and old schema test files ordering issues.


was (Author: rhusar):
So this is a couple of issues together. They mostly come from the restrictions of XSD and its state machine..

{quote} The type has an 'all' model group in its \{content type\} and thus cannot be derived from a non-empty type, since this would produce a 'sequence' model group containing the 'all' model group; 'all' model groups are not allowed to appear inside other model groups.{quote}

In short, the order needs to be forced if we want to continue using derived/extended types.

So fixing ordering discrepancy between XSD and Writer:
* state transfer in writer and test files
* binary/string-keyed-table in xsd

and
* backup-for/backups XSD discrepancy: both can be actually used simultaneously

...and old schema test files ordering issues.

> Investigate Infinispan test XML files do not validate against XSD yet are parsed ok
> -----------------------------------------------------------------------------------
>
>                 Key: WFLY-2480
>                 URL: https://issues.jboss.org/browse/WFLY-2480
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 8.0.0.CR1
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>             Fix For: 9.0.0.Beta1
>
>
> So one or the other should to change.
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'store'. One of '{"urn:jboss:domain:infinispan:2.0":backups, "urn:jboss:domain:infinispan:2.0":backup-for}' is expected.
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'mixed-keyed-jdbc-store'. One of '{"urn:jboss:domain:infinispan:2.0":backups, "urn:jboss:domain:infinispan:2.0":backup-for}' is expected.
> cvc-complex-type.2.4.d: Invalid content was found starting with element 'binary-keyed-table'. No child element is expected at this point.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)