IX90124: IN META SCENARIOS, DATA LOSS FOR A FIELD MIGHT BE SEEN WHEN THE DECLARED TYPE IS DIFFERENT ON CLIENT AND SERVER.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

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:

    IV47009

  • 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



Rate this page:

(0 users)Average rating

Document information


More support for:

Runtimes for Java Technology
ORB

Software version:

6.0

Reference #:

IX90124

Modified date:

2013-08-22

Translate my page

Machine Translation

Content navigation