When I call writeTo on the result of a Dispatch<SOAPMessage> call I do not get valid results for MTOM messages. If I call my MTOM service directly I get the following response using tcpmon.
HTTP/1.1 200 OK Content-Type: multipart/related; type="application/xop+xml"; boundary="uuid:6c6702b2-f91d-4f40-8b0c-e54679d4a2ab"; start=""; start-info="text/xml" Content-Length: 879 Server: Jetty(6.1.19) --uuid:6c6702b2-f91d-4f40-8b0c-e54679d4a2ab Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"; Content-Transfer-Encoding: binary Content-ID: 1243 --uuid:6c6702b2-f91d-4f40-8b0c-e54679d4a2ab Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-ID: MTOM binary data string --uuid:6c6702b2-f91d-4f40-8b0c-e54679d4a2ab- However, if I call this service using Dispatch<SOAPMessage> and then call writeTo on the result I get the result below. I would expect Content-Type in the first attachment to be application/xop+xml, but it is just test/xml. ------=_Part_0_4334864.1255453561672 Content-Type: text/xml; charset=utf-8 1243 ------=_Part_0_4334864.1255453561672 Content-Type: application/octet-stream Content-ID: content-transfer-encoding: binary MTOM binary data string ------=_Part_0_4334864.1255453561672-- Is this a bug, or am I looking at this incorrectly? We are using the JAX-WS dispatch API to implement a custom proxying solution. I've left out a lot of details as to what I'm trying to accomplish, but if more info would be useful let me know. Also, I can provide a testcase if necessary. Thanks, Chris -- View this message in context: http://www.nabble.com/JAX-WS-Dispatch-MTOM-tp25877121p25877121.html Sent from the cxf-user mailing list archive at Nabble.com.
