[jboss-jira] [JBoss JIRA] (WFLY-2472) jboss-as-xts_1_0.xsd in WildFly modified since EAP release

[ https://issues.jboss.org/browse/WFLY-2472?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-2472: ---------------------------------------- Hello Tom, Yes it is something along those lines - overall the changes need to be reviewed in a but more detail to get to the bottom of the exact change needed. In some cases we have found that actually parsers were supporting features not documented in the schema, in that case we can sometimes get away with just updating the schema in all locations - our main concern is backwards compatibility so if the parser was supporting something then updating the schema is just really updating docs to reflect it. On the other hand once a schema makes it into a Final or GA release it needs to be considered frozen for backwards compatibility purposes and only compatible changes should be made at that point e.g. correcting documentation. At this point any schema changes in WildFly should actually result in a schema in the 2.x range (All should be no more than 2.0 at this point as we have not had the first Final release) - this then leaves EAP free to continue to add additional 1.x schemas without conflict. Of course if we know a change being made to a subsystem is going to be made in exactly the same way in EAP we can sometimes add a 1.x schema to WildFly and add the same to EAP. Sorry for not being precise with a response, unfortunately this area is a little complex with some decisions needed on a case by case basis with the main rule being compatibility once it reaches a GA or Final release. In this case it is about the additional elements added in WildFly - a configuration based on that schema that is working in WildFly would fail on EAP despite the schema with the same namespace being supported on EAP. Maybe also get a thread started in wildfly-dev(a)lists.jboss.org - I can be contacted in IRC but we may also want some input from Brian as well. -- 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