Forum Discussion
Is that wsdl file public ? If so, provide the link if possible.
Which version of the tool are you using?
Yeah as nmrao said - would help a lot if you can publish the whole .wsdl file - I've been trying to put the info/content together from the screenshots you've provided and I'm not getting anywhere.
I did a quick check of all the .wsdl's on my harddrive and none of them even use a schemalocation attribute definition in the .wsdls <types> element - in actual fact - none of the .wsdls even use the schemalocation attribute at all, never mind just in the <types> element
its a long shot without seeing your .wsdl - but I'd try and remove the schemalocation attribute reference and any dependency and go from there.
Cheers,
richie
- DJ_Se6 years agoNew Contributor
It is not a public wsdl.
I am attaching a copy of the wsdl file , had to change the servername and port details. Not sure if you would be able to import the definition
- richie6 years agoCommunity Hero
Hey DJ_Se
Ok - I dont see this very often although I'm aware you can do it - you have your xml schema content (typically .xsd extension) embedded within your .wsdl file.
The XML schema content is held within your wsdls <type> element - the schema detail is saved within the <schema> tag and I think this is confusing the issue somewhat.
Also - you are importing namespaces which adds another bit of complication - your schema detail references other namespaces and schemas - this is I reckon whats causing you the problems.
Anyway - the short answer is that your wsdl file is currently schema invalid - yes its wellformed, but it's invalid relative to the imported schemas - I'm talking schema valid relative to the cmn schema - there might be other reasons for it being invalid - thats just the first issue identified (it could be the last though).
If you can supply the imported schemas I can probably edit the file so its no longer invalid - it'll take me a couple of hours - but is possible - but that could significantly change the wsdl file (the schema content in the wsdl file) depending on what changes I have to make.
If I were you, Id go back to the developers who supplied the wsdl file and explain that the .wsdl file (the schema detail in the wsdl file) needs to be valid before you can successfully load it into ReadyAPI!/SoapUI and ask can they edit the file in accordance with the requirements to ensure the schema detail contained within the wsdl file is schema valid?
Im happy to give me altering the file a go to try and get it valid in the meantime - but I''m gonna need those imported schemas first!
WOW - its been a while since I answered a question - feel like I've spent the last 2 weeks just asking them! :)
Cheers,
richie
Related Content
- 6 years agoJfosker
- 9 years agojkgupta0003