BusinessWorks reports unresolved namespaces in WSDL even when WSDL is valid.
Article ID: KB0085905
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Description:
When Schema element is used to create an internal schema, it is unable to resolve namespaces though they are declared at the top.
Symptoms:
During the WSDL import or validation, BW reports, “can't resolve namespace” error in Designer.
Cause:
This is caused by missing namespaces at the internal schema scope.
When Schema element is used to create an internal schema, it is unable to resolve namespaces though they are declared at the top.
Symptoms:
During the WSDL import or validation, BW reports, “can't resolve namespace” error in Designer.
Cause:
This is caused by missing namespaces at the internal schema scope.
Issue/Introduction
BusinessWorks reports unresolved namespaces in WSDL even when WSDL is valid.
Resolution
Add the missing namespaces within the internal schema scope by using import. For example:
<xs:schema attributeFormDefault = "unqualified" elementFormDefault = "unqualified" targetNamespace = "http://cge.concur.com/EAI">
<xs:import namespace = "http://www.concur.com/EAI/xsd" schemaLocation = "Profile.xsd"/>
<xs:import namespace = "http://www.concur.com/EAI/xsd" schemaLocation = "SoapFault.xsd"/>
<xs:schema attributeFormDefault = "unqualified" elementFormDefault = "unqualified" targetNamespace = "http://cge.concur.com/EAI">
<xs:import namespace = "http://www.concur.com/EAI/xsd" schemaLocation = "Profile.xsd"/>
<xs:import namespace = "http://www.concur.com/EAI/xsd" schemaLocation = "SoapFault.xsd"/>
Feedback
Yes
No
Powered by
