CODEWITHSUNDEEP
javaspring-wsaxiom
Nick Foote
Nick Foote

Reputation: 2495

AxiomSoapMessageCreationException: Unknown content type 'application/wsdl+xml'

Anyone have any idea what the following Exception might mean?

I can't find "wsdl+xml" anywhere in our project, not sure where its coming from?

org.springframework.ws.soap.axiom.AxiomSoapMessageCreationException: Unknown content type 'application/wsdl+xml'
at org.springframework.ws.soap.axiom.AxiomSoapMessageFactory.getSoapEnvelopeNamespace(AxiomSoapMessageFactory.java:287)
at org.springframework.ws.soap.axiom.AxiomSoapMessageFactory.createAxiomSoapMessage(AxiomSoapMessageFactory.java:247)
at org.springframework.ws.soap.axiom.AxiomSoapMessageFactory.createWebServiceMessage(AxiomSoapMessageFactory.java:218)
at org.springframework.ws.transport.AbstractWebServiceConnection.receive(AbstractWebServiceConnection.java:86)
at org.springframework.ws.client.core.WebServiceTemplate.doSendAndReceive(WebServiceTemplate.java:553)
at org.springframework.ws.client.core.WebServiceTemplate.sendAndReceive(WebServiceTemplate.java:502)
at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:351)
at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:341)

Upvotes: 2

Views: 1537

Answers (1)

Artem Bilan
Artem Bilan

Reputation: 121382

It comes from the server side:

AbstractWebServiceConnection.receive(AbstractWebServiceConnection.java:86)

Ideally it would be better, if you will persuade the server team to change the content-type header, although you may try to intercept the response from the WebServiceConnection implementation.

However you might send the wrong request, e.g. not to the service URL, but WSDL.

Upvotes: 1

Related Questions