WSE 3.0: MTOM response mandatory for MTOM request?

Hi,

I have a problem calling an MTOM-capable Java WS from .NET 2.0 + WSE3.0.

The client uploads some binary data using MTOM, the server answers with a simple status code, that is not MTOM encoded. It seems however that the .NET client needs an MTOM response for an MTOM request:

System.FormatException: WSE839: An HTTP response was received that used the following content type: text/xml;charset=UTF-8. The following content type was expected: multipart/related; type=application/xop+xml.

The obvious and working workaround was to send some dummy binary data in the response that forces MTOM encoding at the Java server side.

My question is: can the .NET client be configured not to expect an MTOM response for an MTOM request

Thanks:

Gabor

.NET Development1

Unfortunately no, the WSE client requires each request/response pair to have the same MTOM encoding.

Hi, Imre

Would you pls send me one client sample code for MTOM
I am one new guy to C# and WSE. Now I don't know how can I migrate my WSE1.0 program to WSE 3.0

Thanks

Hi, if you download and install WSE 3.0, it includes an MTOM sample, I used that one.

Gabor

I'm having the same problem. Does Microsoft have any plans to fix this This is a bug, right The MTOM/XOP spec doesn't dictate that a synchronous reply to an MTOM/XOP encoded message use the same Content-Type does it It is kind of bogus to force the server to respond with a dummy attachment just to work around this.

I have to invoke an Axis2 Web Service. The service accepts MTOM upload requests and replies with plain (NO MTOM) responses. How can I invoke the service with .NET 2.0 client
With WSE 3.0 client I get the WSE839 Exception. The client expects MTOM response!

Thanks

Nathan ,

Do you know is WCF has the same behavior related to the content type encoding behaviour in the request / respsonse

regards

I had the same problem when using WSE3 to connect to a Java service. When I switch back to use SoapHttpClientProtocol, the problem is gone. Turn the WSE 3 off, and add web reference.

Hi all
I have the same problem using WSE 3.0 and EJB3.0 Webservices.

the exception I get says that client find the message of type "multipart/related; type=\"text/xml\" ......" but expected of type "text/xml"

can anyone tell me what's the problem

the message is as follows:

Client found response content type of 'multipart/related; type="text/xml"; boundary="----=_Part_0_21042659.1197357092550"', but expected 'text/xml'.

is this a bug or I made something wrong

thank you all