[ https://issues.jboss.org/browse/WFLY-2480?page=com.atlassian.jira.plugin.... ] 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. -- This message was sent by Atlassian JIRA (v6.3.11#6341)