Incorrect request in TIBCO BusinessWorks serviceagent when using Undescribed Headers.
Article ID: KB0093487
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Resolution:
Recommended. WSDL Messages intended for Undescribed Headers should have unique part names. If this is not followed, there can be ambiguity in resolving SOAP headers and in the Context Mapping.
>>>>>>>>>>>>>>>>>>>
Check if you have defined the Undescribed Headers as a separate Message element in the abstract WSDL and if you are using this Message Element in the Service agent's Input Header(undescribed header). If not, define a separate Message element and use this element as an Undescribed Header.
As per the TIBCO BusinessWorks documentation:
>>>>>>>>>>>>>>>>>>>Recommended. WSDL Messages intended for Undescribed Headers should have unique part names. If this is not followed, there can be ambiguity in resolving SOAP headers and in the Context Mapping.
>>>>>>>>>>>>>>>>>>>
Check if you have defined the Undescribed Headers as a separate Message element in the abstract WSDL and if you are using this Message Element in the Service agent's Input Header(undescribed header). If not, define a separate Message element and use this element as an Undescribed Header.
Issue/Introduction
Incorrect request in TIBCO BusinessWorks serviceagent when using Undescribed Headers.
Feedback
Yes
No
Powered by
