[midPoint] SOAP API: WSDL File

[Radovan Semancik]

Hi,

I have heard similar reports that the WSDL/XSDs generated in runtime 
might be problematic. It works in some tools but does not work in other. 
This WSDL/XSD is genrated by CXF in runtime and I have to admit that it 
is still a bit a mystery to me how exactly it is generated.

If you need to have reliable interface definition then forget about the 
runtime-generated WSDL. Please use the WSDL and XSD that is bundled in 
midPoint distribution. In the binary packages there is a schema/ 
directory that contains all the required WSDLs and XSDs that have 
schemaLocations set up using relative filesystem paths. This is ideal 
for importing into development tools or integrating into your client 
code build.

Also there is a pre-build SOAP client for Java: 
https://wiki.evolveum.com/display/midPoint/Model+Web+Service+Client

-- 
Radovan Semancik
Software Architect
evolveum.com



On 03/31/2016 05:29 PM, Beat Rohrer wrote:
> We're evaluating midPoint's APIs for use at our university. I've 
> studied the WSDL file at 
> http://localhost:8080/midpoint/ws/model-3?wsdl but I miserably fail 
> when I try to parse it with anything in my toolchain (i.e. Visual 
> Studio, WSDL.exe, New-WebServiceProxy, wsdl2phpgenerator, 
> https://www.wsdl-analyzer.com).
>
> Wsdl.exe tells me:
>
> "There was an error downloading 
> 'http://localhost:8080/midpoint/ws/xml.xsd'. --> The request failed 
> with HTTP stat
> us 404: Not Found.
>
> Error: Unable to import binding 'modelBinding' from namespace 
> 'http://midpoint.evolveum.com/xml/ns/public/model/model-3'
>   - Unable to import operation 'getObject'.
>   - The element 
> 'http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-3:name' 
> is missing."
>
> The other tools report similar errors.
>
> Is there a general problem with the WSDL file, is our test 
> installation not properly configured, do I have to edit the WSDL file 
> manually, or do I need to make adjustments to my tools?