Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1212941

Summary: Schema compatibility broken with updates to jboss-as-messaging_1_4.xsd
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Darran Lofthouse <darran.lofthouse>
Component: JMSAssignee: Tomas Hofman <thofman>
Status: CLOSED EOL QA Contact: Miroslav Novak <mnovak>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: cdewolf, jawilson, jmesnil, thofman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:45:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Darran Lofthouse 2015-04-17 17:49:21 UTC 
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.
Comment 2 Tomas Hofman 2015-04-22 09:45:21 UTC 
Jeff already created a commit, so I'm just creating PR:

https://github.com/jbossas/jboss-eap/pull/2397
Comment 4 Darran Lofthouse 2015-09-23 11:18:11 UTC 
Do we have any update on this one?  The strategy around this bug was designed to minimise the number of EAP releases out there that would be writing an invalid configuration out.
Comment 5 Tomas Hofman 2015-09-24 09:39:48 UTC 
Jimmy is there something that prevents this from being acked?
Comment 6 Mike McCune 2016-03-28 23:39:55 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 8 Red Hat Bugzilla 2023-09-14 02:58:11 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days