IBM Support

JR49579: WRONG BUSINESS OBJECT IS GENERATED IN WEB SERVICE INTEGRATION GENERATE TYPES FUNCTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For a  WSDL that contains two levels of wrapped lists,  when
    the Generate Types function of Process Designer is  used to
    generate business objects from that WSDL, the generated
    business object loses one of the lists. For example:
    
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;<xsd:complexType name="TestBOTestCase1">
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;  <xsd:sequence>
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452; <xsd:element maxOccurs="unbounded" minOccurs="0"
    name="field1" type="bons0:
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;TestBO2TestCase1"></xsd:element>
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;  </xsd:sequence>
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;</xsd:complexType>
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;<xsd:complexType name="TestBO2TestCase1">
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;  <xsd:sequence>
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452; <xsd:element maxOccurs="unbounded" minOccurs="0"
    name="field2" type="xsd:string"><
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;/xsd:element>
     &#65443;&#65506;&#65410;&#65452;&#65506;&#65410;&#65452;  </xsd:sequence>
    </xsd:complexType>
    
    The complex type TestBOTestCase1 is an array list of
    TestBO2TestCase1 with a wrapper.
    The complexType TestBO2TestCase1 is an array list of string
    with a wrapper.
    But the generate function processed the TestBOTestCase1 as an
    array list of string with a wrapper. As a result, the
    TestBO2TestCase1 was lost.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM Business Process Manager                *
    ****************************************************************
    * PROBLEM DESCRIPTION: For a  WSDL that contains two levels    *
    *                      of wrapped lists,  when                 *
    *                      the Generate Types function of          *
    *                      Process Designer is  used to            *
    *                      generate business objects from that     *
    *                      WSDL, the generated                     *
    *                      business object loses one of the        *
    *                      lists. For example:                     *
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;<xsd:complexType
    *                      name="TestBOTestCase1">                 *
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;  <xsd:sequence>
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172; <xsd:element maxOccurs="unbounde
    *                      minOccurs="0"                           *
    *                      name="field1" type="bons0:              *
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;TestBO2TestCase1"></xsd:element>
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;  </xsd:sequence>
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;</xsd:complexType>
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;<xsd:complexType
    *                      name="TestBO2TestCase1">                *
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;  <xsd:sequence>
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172; <xsd:element maxOccurs="unbounde
    *                      minOccurs="0"                           *
    *                      name="field2" type="xsd:string"><       *
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;/xsd:element>
    *                       &#163;&#226;&#130;&#172;&#226;&#130;&#172;  </xsd:sequence>
    *                      </xsd:complexType>                      *
    *                      The complex type TestBOTestCase1 is     *
    *                      an array list of                        *
    *                      TestBO2TestCase1 with a wrapper.        *
    *                      The complexType TestBO2TestCase1 is     *
    *                      an array list of string                 *
    *                      with a wrapper.                         *
    *                      But the generate function processed     *
    *                      the TestBOTestCase1 as an               *
    *                      array list of string with a wrapper.    *
    *                      As a result, the                        *
    *                      TestBO2TestCase1 was lost.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a complex type contains only one element and the element
    is an array list, the business object is generated correctly.
    But if there are two or more levels of wrapped lists, the
    business object is not generated correctly.
    

Problem conclusion

  • A fix is available for IBM Business Process Manager V7.5.1.1.
    After this fix is applied, no matter how many levels of
    wrapped lists are contained,  the correct business object is
    generated, showing the correct relationship  among the arrays.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR49579:
      1. Select Business Process Manager with your edition from the
    product selector, the installed version to the fix pack level,
    and your platform,  and then click Continue.
      2. Select APAR or SPR, enter JR49579, and click Continue.
    
    When you download 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 number

    JR49579

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-11

  • Closed date

    2014-05-15

  • Last modified date

    2014-05-15

  • 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

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 May 2014