Forum Discussion
SmartBear_Suppo
Alumni
15 years agoHi!
Most of these WSDLs have schemas that refer to some type that hasn't been defined; this can be either because the defining schema was not imported correctly or because the type reference itself is incorrect (missing namespace, misspelled, etc). One of them has a schema error in the WSDL itself, and the second and third entries (which are the same) worked fine to import.
We know the error messages given by soapUI are really bad here, hope to improve them for the next release
Unfortunately we don't have any feature for importing many files at once, but you could pretty easily create a groovy script that does that for you.
regards!
/Ole
eviware.com
Most of these WSDLs have schemas that refer to some type that hasn't been defined; this can be either because the defining schema was not imported correctly or because the type reference itself is incorrect (missing namespace, misspelled, etc). One of them has a schema error in the WSDL itself, and the second and third entries (which are the same) worked fine to import.
We know the error messages given by soapUI are really bad here, hope to improve them for the next release
Unfortunately we don't have any feature for importing many files at once, but you could pretty easily create a groovy script that does that for you.
regards!
/Ole
eviware.com