IBM Support

PM48791: IN BO COMPATIBILITY MODE, WSDL RPC STYLE NEEDS TO BE CONVERTED TO DOC/LITERAL STYLE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In business object (BO) compatibility mode, WSDL RPC style
    needs to be converted to Doc/literal style
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the SDO API in IBM WebSphere       *
    *                  Application Server V8.0 and WebSphere       *
    *                  Process Server                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: When running a mediation flow, the      *
    *                      float value 2.0 becomes NaN             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When running a mediation flow in Lazy Mode with input float
    value 2.0, the output becomes NaN value.
    This problem is caused by a data mapping rule that has no
    visibility to the input data. The input data is under a custom
    namespace invisible to the end users as a result of the
    process of mapping a WSDL document to an XML schema. Under
    Lazy Mode, if a WSDL document targets namespace
    "http://www.example.org/wsdl", then a WSDL <message> element
    is mapped to an SDO type under the custom namespace
    "wsdl.http://www.example.org/wsdl" and a child <part> element
    is mapped to an SDO property which in the underlying schema is
    represented by a local unqualified element in no namespace. In
    Eager Mode, however, a WSDL <part> element is mapped to a
    qualified local element in the actual namespace
    "http://www.example.org/wsdl". The Lazy Mode behavior must
    match this output so that data mapping rules can operate
    correctly in both modes.
    

Problem conclusion

  • The WSDL mapping to XML schema has been corrected such that
    the WSDL <part> element will be mapped to an element in the
    expected namespace.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.2.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM48791

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-09-27

  • Closed date

    2011-09-27

  • Last modified date

    2011-09-29

  • APAR is sysrouted FROM one or more of the following:

    PM24443

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021