Keith,
This is an XML namespace issue. The targetNamespace attribute at the
start of the file defines the namespace that all the definitions you define
in your WSDL file will be in. Whenever you reference any of these
definitions
you must use the correct namespace prefix, in your case the tns
I've had the same problem when using the wsdl4j toolkit. If you step through
the Definition returned from the wsdl4j toolkit, you'll find that it doesn't
find the referenced binding node - because it is looking in a different
namespace. I've found this problem with a good subset of the wsdl files
