Bug 1104304

Summary: [GSS] (6.2.x) JBoss Marshalling should not require classes for null fields
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brad Maxwell <bmaxwell>
Component: RemotingAssignee: David M. Lloyd <david.lloyd>
Status: CLOSED DEFERRED QA Contact: Jitka Kozana <jkudrnac>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.2.0CC: cdewolf, jawilson, kkhan, rsvoboda, smumford
Target Milestone: ER6   
Target Release: EAP 6.2.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
With this change: An object that is marshalled / unmarshalled using JBoss Marshalling, such as a remote EJB invocation, where the object has a field whose value is null, the fields class type is not required on the other side during unmarshalling since it has no value. This fix prevents ClassNotFound exceptions from occuring during unmarshalling of an object where the object version may be different and not contain the class defintion of the field whose value is null.
Story Points: ---
Clone Of: 1102271 Environment:
Last Closed: 2014-06-16 13:23:54 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:
Bug Depends On: 1102271    
Bug Blocks: 1104306, 1113768    

Description Brad Maxwell 2014-06-03 17:56:46 UTC
+++ This bug was initially created as a clone of Bug #1102271 +++

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.