APAR status
Closed as program error.
Error description
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
Local fix
Problem summary
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.
Problem conclusion
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.
Temporary fix
Comments
APAR Information
APAR number
IX90124
Reported component name
ORB
Reported component ID
620700123
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-13
Closed date
2013-08-22
Last modified date
2013-08-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
ORB
Fixed component ID
620700123
Applicable component levels
R600 PSY
UP
R260 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC9HBB","label":"ORB"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 August 2013