Red Hat Bugzilla – Bug 1102271
[GSS] (6.3.x) JBoss Marshalling should not require classes for null fields
Last modified: 2014-08-06 10:34:38 EDT
If an object contains a field whose value is null, the field's object type should not be loaded / instatiated since it has no value.
Clarified the doc text change a bit.
First, sorry for late notice. EAP 6.3.0.ER9 contains JBoss Marshalling 1.4.6, which indeed fixes this issue (JBMAR-161), which is why I'm marking this as verified. However, the customer case linked from this bugs requires additional fixes for JBMAR-162: one fix is included in JBoss Marshalling 1.4.7 and the other was not released in 1.4.x branch yet. So here's the warning: if EAP 6.3 remains on Marshalling 1.4.6, the customer case _won't_ be fixed. (I know there is a one-off patch for 6.2, but providing a warning seems to be a good idea anyway.)
This release note should describe https://issues.jboss.org/browse/JBMAR-161 Brad, can you please review the following proposed release notes text? The change is based on the last paragraph in this Bug comment: https://bugzilla.redhat.com/show_bug.cgi?id=1123331#c0 Proposed release notes text: In previous releases of Red Hat JBoss EAP 6, if an object contained a field whose value was null or of a different object type than the field, attempts to load the field's object type could cause unmarshalling operations to fail. This issue has been corrected in this release of the product.
Spoke with Brad and we talked about this: In previous releases of Red Hat JBoss EAP 6, if an object contained a field whose value was null and the object type of the field did not exist on the unmarshalling side, attempts to load the field's object type could cause unmarshalling operations to fail with a ClassNotFoundException for ClassOnlyOnMarshallingsSide. This issue has been corrected in this release of the product.
Replaced it with Brad's text.