JR48364: WRONG NAMESPACE USED IN SOAP REQUEST BY OUTBOUND WEB SERVICE ‚  INTEGRATION

Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products
Download Version 8.0.1 Fix Pack 3 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• When a client uses an outbound web service integration with a
  list item, the SOAP request that is generated might contain an
  invalid namespace. Following the SOAP standard, the element
  should use the parent namespace instead of type namespace. And
  the list item should use the type namespace. ﾂ ﾠ
  

Local fix

• manually edit the business objects
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Business Process Manager Advanced and   *
  *                  Standard                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: In the example, if the error happened   *
  *                      the output would be similar to the      *
  *                      following output:                       *
  *                      <ns1:wrapper                            *
  *                      xmlns= &#162;&#226;&#130;&#172;  &#189;http://example.com/wrapperE
  *                      pl                                      *
  *                      e &#162;&#226;&#130;&#172;  &#189;
  *                      xmlns:arr= &#162;&#226;&#130;&#172;  &#189;http://example.com/arra
  *                      am                                      *
  *                      ple &#162;&#226;&#130;&#172;  &#189;
  *                      xmlns:ns1= &#162;&#226;&#130;&#172;  &#189;http://example.com/arra
  *                      am                                      *
  *                      ple &#162;&#226;&#130;&#172;  &#189;>
  *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172; &#163;&#226;&#130;&#172;&#226;&#130;&#172; <arr:double>123.1</arr:d
  *                      </ns1:wrapper>                          *
  *                      The error occurs because of an XML      *
  *                      processor code issue. The array item    *
  *                      is the element of the array wrapper;    *
  *                      therefore, the array item should use    *
  *                      the namespace of the wrapper type.      *
  *                      The namespace of the parent element     *
  *                      is used by mistake.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During web service integration, when the output contains an
  array but the array type ( &#162;&#226;&#130;&#172; &#147;ArrayOfdouble &#162;&#226;&#130;&#172;  &#189; in exampl
  the
  related element ( &#162;&#226;&#130;&#172; &#147;wrapper &#162;&#226;&#130;&#172;  &#189; in example) are in diffe
  namespaces, then the wrong namespace might be used for the
  element ( &#162;&#226;&#130;&#172; &#147;wrapper &#162;&#226;&#130;&#172;  &#189; in the example).
  For example, the element that is defined as
  <xsd:complexType name="wrapperElement">
  <xsd:sequence>
  <xsd:element minOccurs="0" name="wrapper"
  nillable="true" type="q1:ArrayOfdouble"
  xmlns:q1="http://example.com/arrayExample"/>
  </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="wrapperElement" nillable="true"
  type="tns:wrapperElement"/>
  is in the namespace http://example.com/wrapperExample.
  However, the array is defined as
  <xsd:complexType name="ArrayOfdouble">
   &#163;&#226;&#130;&#172;&#226;&#130;&#172; &#163;&#226;&#130;&#172;&#226;&#130;&#172;<xsd:sequence>
  <xsd:element minOccurs="0" maxOccurs="unbounded"
  name="double" type="xsd:double"/>
  </xsd:sequence>
  </xsd:complexType>
  <xsd:element name="ArrayOfdouble" nillable="true"
  type="tns:ArrayOfdouble"/>
  under the namespace http://example.com/arrayExample.
  The correct SOAP request should be generated as
  <wrapper xmlns= &#162;&#226;&#130;&#172;  &#189;http://example.com/wrapperExample &#162;&#226;&#130;&#172;  &#189;
  xmlns:arr= &#162;&#226;&#130;&#172;  &#189;http://example.com/arrayExample &#162;&#226;&#130;&#172;  &#189;>
   &#163;&#226;&#130;&#172;&#226;&#130;&#172; &#163;&#226;&#130;&#172;&#226;&#130;&#172; <arr:double>123.1</arr:double>
  </wrapper>
  

Problem conclusion

• After the fix is applied, the namespace of the wrapper type is
  used.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR48364. After you select the product group, product,
  installed version, and platform, click Continue and then
  select APAR or SPR, enter JR48364, and click Continue. When
  downloading fix packages, ensure that you also download the
  readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

Temporary fix

Comments

APAR Information

• 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 STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R800 PSY

     UP