Closed as program error.
Error Message: In meta scenarios, data loss for a field might be seen when the declared type is different on client and server. Note that data loss won't be seen for cases where the declared type on the sender isAssignableFrom the declared type on the receiver. . Stack Trace: N/A . One common instance of the problem being - XML file loosing data while serialization and de-serialization when meta callback is trigerred for the following two classes -: org.apache.xerces.dom.AttributeMap org.apache.xerces.dom.NamedNodeMapImpl
For meta scenarios, data loss is occurring when the field declared type is different on client and the server side and the declared type on the sender is not AssignableFrom the declared type on the receiver, However the runtime type isAssignableFrom the declared type on the receiver. This can be achieved by over-riding the readObject and writeObject methods appropriately.
This defect will be fixed in: 5.0.0 SR16 FP4 6.0.0 SR15 6.0.1 SR7 7.0.0 SR6 . Modify the isAssignableFrom check to be on the runtime value of the field rather than the declared type.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels