I've had some experience using SOAP::WSDL, including bug fixes.

The message you're getting is just a warning, as the schemaLocation attribute (the URI for the xsd) is missing (it's optional).

However, I found that wdsl2perl actually bombs with the error:

"unsupported global type <xsd:string> found in part extID at /usr/local/share/perl/5.8.8/SOAP/WSDL/Generator/Iterator/WSDL11.pm line 75."

This is caused by the WSDL element:

<wsdl:part name="extID" type="xsd:string">

This implies document/literal semantics which is not alloed if the WSDL is to meet the WS-I standard. (Hell, I'm bluffing - I can't remember exactly what that means :)

Anyway, SOAP::WSDL is quite strict about adhering to the WS-I standard. I think this allows it to cover a manageable amount of functionality.

The WSDL looks like it was auto-generated - can you say which tools were used to generate it?

Using tools such as Apache Axis will (I believe) generally lead to success as it should produce WS-I compliant WDSL.

The problem with SOAP::Lite is that it simply doesn't handle complex types.