I have often problems with Designer : some WSDL can not be discovered.
Obviously, it’s because it’s not use compliance WSDL and I understand.
However in SOAP UI, the software can discover and even allow to use the WSDL to generate query.
For instance, in attached file bellowed, I have the following WSDL. I have no problem to discover it in SOAP UI but it’s impossible de generate a web service descriptor in designer.
It’s an Oracle financial fusion application WSDL.
I can modify it to change some element tags to allow designer to generate descriptor.
Even like that I can not called the wished method (in my cas runReport) because of the fact that in WSDL some tags are required and Integration server refused to connect to the server to call the method if I delete theses tags in my soap enveloppe because of the soap enveloppe should be complianced using IS. In SOAP UI it’s not required. If a parameter is missing and if it’s necessary, we received an error in http response or in soap response. IS refused to do that.
But even in my case, if I accept to fill all required parameters, I have a policy problem.
It’s weird for me that a software like SOAP UI can do things that IS is not abled to do.
To solve my problem, I have no other solution to call pub.client:http service and create the soap enveloppe my self. And that works.
I imagine (hope) that exist some parameter to allow IS to not do some control in client side but I don’t know how/
ExternalReportWSSService.wsdl (130 KB)