Re: [wildfly-dev] Support for legacy xml parsers
Ha, I just saw this email after having a conversion with Tomaz and David
on IRC.
Since WildFly there was such a long time between 7.1.1.Final and WildFly
8 I think it might be better to wait until WildFly 10. I still see quite
a few questions regarding JBoss AS 7.x. If we could encourage those
users to switch to WildFly I think it would make all of us happier :) If
we cut support for WildFly 9 of their configuration files I could see
them less likely to move if 9 is the current release.
On 07/24/2014 08:50 AM, Brian Stansberry wrote:
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.
--
James R. Perkins
JBoss by Red Hat