Different SOAP versions?

MIP
, ,
1

I’ll try it again. Maybe the headline was a bit misleading from https://developer.milestonesys.com/s/question/0D53X000067shGUSAY/generating-code-from-wsdl.

We have a Java application and implement the SOAP interface directly.

The following URLs work fine:

The following 2 URLs do not work:

The server responds there with an HTTP error 415 - “Cannot process the message because the content type ‘text/xml; charset=utf-8’ was not the expected type ‘application/soap+xml; charset=utf-8’”.

Why is there a difference between AD and Basic mode on same service ?

Can it be that the server expects SOAP 1.2?

The code generated from the WSDL is just SOAP 1.1.

Is it possible that the SOAP 1.2 declaration in the WSDL file is incorrect?

The Java library definitely supports SOAP 1.2.

Thomas

2

There are several extensions in the WSDL definitions for SOAP 1.2. These can not be resolved and nothing is generated.

You can set a flag on the generator in Java to ignore the errors and generate appropriate wrapper code, but this will cause Problems/exceptions at runtime.

Why are custom extensions used so that the WSDL can not be used outside of C# ?

3

Unfortunately it is not really possible to do what you are trying.

The services you have listed, can be accessed from your Java SOAP client, either because it is “ordinary” soap services (.asmx) or WFC service (.svc) using BasicHttpBinding.

This binding works for for basic users where we require SSL/TLS and thus don’t send credentials unencrypted on the network.

The combination of WCF services (.svc) and AD does not work with your Java client because these endpoints use wsHttpBinding with message based encryption - and unfortunately this is not possible to consume from a non-WCF web client.