Unable to import MDM WSDL into Visual Studio due to validation errors.
book
Article ID: KB0092706
calendar_today
Updated On:
Products
Versions
TIBCO MDM
-
Not Applicable
-
Description
Description: When importing MDM WSDL into Visual Studio for .NET integration, the following errors are thrown:
Cannot import wsdl:binding Detail: There was an error importing a wsdl:portType that the wsdl:binding is dependent on. XPath to wsdl:portType: //wsdl:definitions
[@targetNamespace='http://www.tibco.com/cim/services/mastercatalogrecordworkitem/wsdl/2.0']/wsdl:portType[@name='CIMPortType'] XPath to Error Source: //wsdl:definitions
Warning 31 Custom tool warning: Cannot import wsdl:portType Detail: An exception was thrown while running a WSDL import extension: System.ServiceModel.Description.XmlSerializerMessageContractImporter Error: The datatype 'http://www.tibco.com/cim/services/mastercatalogrecord/wsdl/2.0:IdentityType' is missing. XPath to Error Source: //wsdl:definitions
Warning 25 Custom tool warning: There was a validation error on a schema generated during export: Source: Line: 139 Column: 8 Validation Error: Type 'http://www.tibco.com/cim/services/mastercatalogrecord/wsdl/2.0:ExternalKeysType' is not declared. C:
Warning 26 Custom tool warning: There was a validation error on a schema generated during export: Source: Line: 141 Column: 8 Validation Error: Type 'http://www.tibco.com/cim/services/mastercatalogrecord/wsdl/2.0:ReturnType' is not declared. C:\Corporate2\RPC\Main
Warning 27 Custom tool warning: There was a validation error on a schema generated during export: Source: Line: 142 Column: 8 Validation Error: Type 'http://www.tibco.com/cim/services/mastercatalogrecord/wsdl/2.0:EntityDataType' is not declared. C:\Corporate2\RPC
Unable to import MDM WSDL into Visual Studio due to validation errors.
Resolution
The Visual Studio used is an older version and is based on .NET 2.0. As such, the WSDL can not be added as Service Reference. The issue is resolved after adding it as .NET 2.0 Web Reference.