[wildfly-dev] Support for legacy xml parsers

For WildFly 9 (not 8.2) I propose that we change our policy regarding support for legacy WildFly configuration documents.[1] Currently we support being able to parse content from any of our namespaces (core or subsystem) shipped in a final release going back to AS 7.0.0. I want to change this to limit support to namespaces shipped in AS 7.2.0 or later and EAP 6.1.0 or later. This cutoff is consistent with what we are doing with mixed-version support in managed domains. The goal of this is to reduce the maintenance burden related to legacy xml parsers. The goal is *not* to reduce the size of the codebase etc. So, if this proposal carries, please do not go off and delete old stuff that works just because you can. But, if you find yourself having to expend energy maintaining one of these old parsers, the policy change means just dropping it is a valid alternative. Comments? [1] Configuration documents meaning standalone/domain/host.xml, not stuff like deployment descriptors. -- Brian Stansberry Senior Principal Software Engineer JBoss by Red Hat