*** MORE Detail ***
The developers are using JAXB WS which generates a very modular WSDL.
I brought down a local copy of the WSDL, child WSDL, and 3 XSD files.
I was able to get it to process the wsdl and contract by adding a default types element (bold below).
The types element is actually in the child wsdl. processTypes(srcWsdl, wsdlLoc) fails in the root/parent wsdl.
<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.yellow.com/ybbp/api" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" name="MetaverseApiService" targetNamespace="http://www.yellow.com/ybbp/api">
<import namespace="http://www.yellowbook.com/bp/model/api" location="http://localhost/metaverse1.wsdl"/>
<types>
<xsd:schema targetNamespace="http://www.yellowbook.com/ybbp/api" elementFormDefault="qualified"/>
</types>
<binding name="MetaverseApiPortBinding" type="ns1:MetaverseApiPortType" xmlns:ns1="http://www.yellowbook.com/bp/model/api">