Parser support missing for EAP 6.3 version of 'skip-group-loading' ------------------------------------------------------------------ Key: WFCORE-798 URL: https://issues.jboss.org/browse/WFCORE-798 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 2.0.0.Alpha6 Reporter: Brian Stansberry Assignee: Darran Lofthouse Fix For: 2.0.0.CR1 Trying to run WildFly full's ParseAndMarshalModelsTestCase against the EAP 6.3 configs results in failures like this: {code} Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[37,21] Message: WFLYCTL0197: Unexpected attribute 'skip-group-loading' encountered at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117) at org.jboss.as.domain.management.parsing.ManagementXml_Legacy.parseLocalAuthentication_1_3(ManagementXml_Legacy.java:2105) at org.jboss.as.domain.management.parsing.ManagementXml_Legacy.parseAuthentication_1_3(ManagementXml_Legacy.java:1486) at org.jboss.as.domain.management.parsing.ManagementXml_Legacy.parseSecurityRealm_1_3(ManagementXml_Legacy.java:779) at org.jboss.as.domain.management.parsing.ManagementXml_Legacy.parseSecurityRealms(ManagementXml_Legacy.java:649) at org.jboss.as.domain.management.parsing.ManagementXml_Legacy.parseManagement_1_5(ManagementXml_Legacy.java:224) at org.jboss.as.domain.management.parsing.ManagementXml_Legacy.parseManagement(ManagementXml_Legacy.java:151) at org.jboss.as.server.parsing.StandaloneXml_Legacy.readServerElement_1_4(StandaloneXml_Legacy.java:444) at org.jboss.as.server.parsing.StandaloneXml_Legacy.readElement(StandaloneXml_Legacy.java:136) at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:66) at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:47) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) ... 136 more {code} The EAP 6.4 configs have this attribute but don't fail, so it seems the problem is isolated to the 6.3 schema parsing; i.e. urn:jboss:domain:1.6.