Requirement of adding namespaces

[amitavmohanty01]

The WSDL namespaces are:

<wsdl:definitions targetNamespace="urn:DM/services" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:DM/services" xmlns:intf="urn:DM/services" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="urn:DM/types" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

However, when I make SOAP calls there are some WSDLs missing.

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:impl="urn:DM/services" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ins0="urn:DM/types">

I have to specify XSI attributes for some types for which I need soapenc and tns1 namespaces which I had to include manually. Until I had manually included the namespaces, I was getting an error as follows:

The prefix "soapenc" for attribute "soapenc:arrayType" associated with an element type "items" is not bound.

[tjarratt]

@amitavmohanty01 thank you for filing this issue. Would it be possible for you to write a test, or a script that reproduces this behavior? From what you've provided, I'm not entirely sure what might need to change in order to include the namespaces correctly.

Without being able to see your actual WSDL, my best guess is that your WSDL imports another WSDL which declares the soapenc and tns1 namespaces, which is a known defect in Wasabi.

[tjarratt]

Closing due to inactivity.