IBM Support

LI80642: CREATING AN API BASED ON A WSDL FAILS WITH AN UNDEFINED NAMESPACE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • A wsdl contains a wsdl:binding.  Inside the wsdl:binding element
    there is the expected soap:binding.
    In addition, there is a second binding named jms:binding.  This
    second binding is unknown to the parser that processes the wsdl
    and causes an error.
    
    The specific error for the customer reporting the problem was
    
    The following name, jms:binding, was bound to namespace
    undefined in
    http://www.tibco.com/namespaces/ws/2004/soap/binding/JMS. This
    is an unrecognized element, please correct.
    

Local fix

  • The element causing the problem can be commented out in the
    wsdl.
    For example:
    
    
      <wsdl:binding  name="ABCBinding"  type="tns:ABC">
            <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
            <jms:binding messageFormat="Text"/>
            <wsdl:operation name="initiateWithdrawalV1">  ...
    
    
    
    to:
       <wsdl:binding  name="ABCBinding"  type="tns:ABC">
            <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
            <!-- <jms:binding messageFormat="Text"/> -->
            <wsdl:operation name="initiateWithdrawalV1">  ...
    
    
    to avoid the error.
    

Problem summary

  • The action to create an API from WSDL will fail with a message
    similar to:
    
    The following name, jms:binding, was bound to namespace
    undefined in
    http://www.tibco.com/namespaces/ws/2004/soap/binding/JMS. This
    is an unrecognized element, please correct.
    

Problem conclusion

  • The root problem is a logic error in the API Connect generator.
     The problem has been corrected and customers should move to a
    new version of the API Connect product if they experience this
    issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI80642

  • Reported component name

    API CONNECT ENT

  • Reported component ID

    5725Z2201

  • Reported release

    18X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-25

  • Closed date

    2019-03-27

  • Last modified date

    2019-03-27

  • 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

    API CONNECT ENT

  • Fixed component ID

    5725Z2201

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18X","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 March 2019