Description of problem:

Within the EAP 6.4 release unfortunately non-compatible changes have been made to the 1.4 version of the jboss-as-messaging schema.

Parsing of schemas from older versions will still be possible but the issue means configuration written by EAP 6.4 may not be parsed by other servers that already parse a previous version of 1.4.

Unfortunately as releases are out it is impossible to completely fix this but we can undertake the following steps to minimise the impact: -

Immediately add a jboss-as-messaging_1_5.xsd to EAP 6.4 for inclusion in the next CP release.  Revert the changes to the 1.4 xsd but leave the parser still quietly accepting the additional element.

The end result of this will be that provided users upgrade to subsequent CP releases their configuration will be written according to a valid 1.5 schema.


Upstream we will then make the following changes: -

  Forward port the 1.5 schema and parsing.
  Update the 1.4 parser to quietly accept the new element.


This will leave a small window where messaging subsystem configuration written by EAP 6.4.0 will not be usable on WildFly 8.2.0.Final or previous EAP releases that also support 1.4 of the schema - however I think the likelyhood of that transition is low in general.