PI50232: SOAP ADAPTERS GENERATED FROM THE SERVICES DISCOVERY WIZARD ARE UNABLE TO FETCH DATA

IBM MobileFirst Platform Foundation Interim Fix README for 7.1
IBM MobileFirst Platform Foundation Interim Fix README for 7.0
IBM MobileFirst Platform Foundation Interim Fix README for 6.3

APAR status

• Closed as program error.

Error description

• A SOAP adapter generated using the services discovery wizard is
  unable to fetch data from certain end points. The SOAP adapter
  fails with
  "Insufficient Parameters."
  

Local fix

• Modify the generated adapter code as follows:
  For example:
  a)  The generated adapter code has the following root mappings
  :
  
         var mappings = {
          roots: {
              'GetState': { nsPrefix: 's1', type: 's1:GetState' }
          },
          types: {
              's1:GetState': {
                  children: [
                      {'countryId': { nsPrefix: 's1' }}
                  ]
              }
          }
      };
  
    This needs to be changed to :
  
     var mappings = {
          roots: {
              'GetState': { nsPrefix: 'tns', type: 'tns:GetState'
  }
          },
          types: {
              'tns:GetState': {
                  children: [
                      {'countryId': { nsPrefix: 'tns' }}
                  ]
              }
          }
      };
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MobileFirst Platform Foundation developers using SOAP        *
  * adapters                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The SOAP adapter generator creates root and type mappings    *
  * for a given WSDL endpoint.  These mappings reference a       *
  * namespace by its prefix.  The prefix is determined by        *
  * looking through all of the defined namespaces for the one    *
  * that matches the given targetNamespace.  The problem is that *
  * the code is doing an incorrect search on the namespace.  As  *
  * a result of the incorrect search, multiple namespaces met    *
  * the search criteria and the the first one, which was the     *
  * wrong one, was used.                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• In this scenario the namespace search returned two namespaces.
  One with prefix "tns" and another with prefix "s1" with the
  latter being the first found.  However, this search method is
  wrong since the "s1" namespace included the search string, but
  had additional text appended after it.  The code has been
  updated to do a proper namespace search so that only the proper
  match will be returned.  Now the namespace with the "tns" prefix
  will be found and used.
  

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

  MFPF/WORKLIGHT

• Fixed component ID

  5725I4301

Applicable component levels

• R630 PSY

     UP

• R700 PSY

     UP

• R710 PSY

     UP