The standard configs are not using the most up to date version of all schemas
The effect of this is when the user modifies their config via a management action, the config file will be updated to use all the latest config schema namespaces. This will result in changes to the config file unrelated to the management update, which isn't a failure, but is untidy.
https://github.com/jbossas/jboss-eap/pull/72
Stuart Douglas <stuart.w.douglas> updated the status of jira AS7-6780 to Resolved
Verified on EAP 6.1 ER5. All subsystems are using the most up to date schemas.