When using SOAP WS interface, there is one glitch, that prevents rigid software to use WSDL.
Such client searches for URI in path /midpoint/ws/xml.xsd
Here is the reason (lets say localhost:8080 is midPoint installation):
- WS client is pointed to "http://localhost:8080/midpoint/ws/model-3?wsdl"
- this WSDL contains refference to common-3 on proxy-path "http://localhost:8080/midpoint/ws/model-3?xsd=http://midpoint.evolveum.com/xml/ns/public/common/common-3"
- common-3.xsd contains refference to XMLSchema on proxy path "http://idm-test.srv.int.avast.com:8080/midpoint/ws/model-3?xsd=http://www.w3.org/2001/XMLSchema" (the same applies for fault-3)
- XMLSchema contains unproxied reference to xml.xsd on path "xml.xsd"
which leads to request for http://localhost:8080/midpoint/ws/xml.xsd
This info can be nicely seen in SOAP-UI, right click on modelBindig -> WSDL Content -> xml.xsd ("<html> <body>No service was found.</body></html>")