Hi There,
This problem has no doubt long been sorted but for the benefit of others who encounter it I am replying.
Unfortunately I do not know exactly what caused this error for me, but this is how I invoked it:-
When trying to create a new project I tried to load the WSDL on the remote server by populating the 'Initial WSDL' field(on the New SOAP project dialog box) with the URL of the WSDL.
How I got around this error:-
I copied the WSDL folder & associated XSD's folders[apparently our environment is complex] to my local machine & populated the 'Initial WSDL' field with the local WSDL. All worked fine then.
n.b. in our environment the WSDL uses it's own XSD, located in the same folder, and other 'generic' XSD's which are accessed via a relative path from the project WSDL. Consequently I kept the same dir structure that exists on the remote machine for all XSD files - the project XSD & the shared/ generic XSD's - on my local drive.
