IBM Support

JR42192: ADDITIONAL XSI:TYPE ATTRIBUTE INCLUDED IN XML

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • problem with an additional
    'type=' attribute included in XML when it is not needed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of BPM Express, BPM Standard and BPM  *
    *                  Advanced.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: problem with an additional              *
    *                      'type=' attribute included in XML       *
    *                      when it is not needed.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    problem with an additional
    'type=' attribute included in XML when it is not needed.
    The scenario involves a doc/lit style WSDL.  Normally, the
    SOAP request/response for a doc/lit does not include xsi:type
    on the wire because
    this style of WSDL can be validated by the XML schema.  In
    this instance, the customer's endpoint did not like the fact
    that for an int that
    our Axis based SOAP engine was sending xsi:type="xsd:int".
    <myElement xsi:type="xsd:int">11</myElement>
    While this is technically a valid request and would not cause
    validation against the schema to fail, the customer did not
    like.  The fix detects
    this situation for simple types like int and will not add the
    xsi:type if the xsdType is of the standard schema namespace
    (http://www.w3.org/2001/XMLSchema).
    For example, in the case of an int - its XML schema root base
    type is {http://www.w3.org/2001/XMLSchema}decimal .  This
    section of code where
    it adds the xsi:type was mainly for custom derived types.  For
    example, if "myNS:AccountNumber" is derived from "xs:string".
    In our case of int -
    it's not a custom type (e.g. it still has the standard
    http://www.w3.org/2001/XMLSchema namespace).
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR42192

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-09

  • Closed date

    2012-04-18

  • Last modified date

    2012-04-18

  • 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

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
12 October 2021