IBM Support

JR41994: INCORRECT NAMESPACE WHEN USING COMPLEX DATA TYPE FROM TOOLKIT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For Inbound Web Services in BPM 7.5.1, when a complex data
    type from a toolkit is used in the response, the generated
    WSDL attaches an incorrect namespace prefix to this complex
    type.
    
    For example in the soap response below:
    
    <soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <findOpenJobsResponse xmlns="http://BPMUNIT/HRJobsWS.tws">
    <ns1:jobReqs xmlns:ns1="http://TYPESTK">
    <ns1:item>
    <ns1:requistionID>ENG3-QA-TEST</ns1:requistionID>
    <ns1:jobTitle>Automation Test Engineer</ns1:jobTitle>
    <ns1:jobGrade>7</ns1:jobGrade>
    <ns1:minSalary>44000.0</ns1:minSalary>
    <ns1:maxSalary>65000.0</ns1:maxSalary>
    <ns1:status>OPENED</ns1:status>
    </ns1:item>
    </ns1:jobReqs>
    </findOpenJobsResponse>
    </soapenv:Body>
    </soapenv:Envelope>
    
    The namespace of this is incorrect for the jobReqs element,
    since it is defined in the http://BPMUNIT/HRJobsWS.tws
    namespace and should have that namespace, not http://TYPESTK,
    which is where its array type is defined.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of BPM Express, BPM Standard and BPM  *
    *                  Advanced.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: For Inbound Web Services in BPM         *
    *                      7.5.1, when a complex data              *
    *                      type from a toolkit is used in the      *
    *                      response, the generated                 *
    *                      WSDL attaches an incorrect namespace    *
    *                      prefix to this complex                  *
    *                      type.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For Inbound Web Services in BPM 7.5.1, when a complex data
    type from a toolkit is used in the response, the generated
    WSDL attaches an incorrect namespace prefix to this complex
    type.
    For example in the soap response below:
    <soapenv:Envelope
    xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Body>
    <findOpenJobsResponse xmlns="http://BPMUNIT/HRJobsWS.tws">
    <ns1:jobReqs xmlns:ns1="http://TYPESTK">
    <ns1:item>
    <ns1:requistionID>ENG3-QA-TEST</ns1:requistionID>
    <ns1:jobTitle>Automation Test Engineer</ns1:jobTitle>
    <ns1:jobGrade>7</ns1:jobGrade>
    <ns1:minSalary>44000.0</ns1:minSalary>
    <ns1:maxSalary>65000.0</ns1:maxSalary>
    <ns1:status>OPENED</ns1:status>
    </ns1:item>
    </ns1:jobReqs>
    </findOpenJobsResponse>
    </soapenv:Body>
    </soapenv:Envelope>
    The namespace of this is incorrect for the jobReqs element,
    since it is defined in the http://BPMUNIT/HRJobsWS.tws
    namespace and should have that namespace, not http://TYPESTK,
    which is where its array type is defined.
    

Problem conclusion

  • The problem was fixed to use the correct namespace.
    
    The fix is available as a part of the JR42012 ifix package
    (http://www-01.ibm.com/support/docview.wss?uid=swg1JR42012)
    and needs to be installed as follows:
    - Install JR42012 on both Process Designer and Process
    Center/Server using IM
    - On Process Center/Server run bpmprofileUpgrade as outlined in
    http://www-01.ibm.com/support/docview.wss?uid=swg27022245#recove
    rFailure
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR41994

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-21

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

  • Fixed component ID

    5725C9500

Applicable component levels

  • R750 PSY

       UP

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

Document Information

Modified date:
07 October 2021