We are using mtom via CXF/JAXB with DataHandler. In some scenarios our service is supposed to respond with a null DataHandler.
The interesting thing is that when DataHandler is null, there is no referencing element in the soap response, just the uuid that follows normally as the header for the attachment. For instance: HTTP/1.1 200 OK Date: Mon, 16 Apr 2012 21:36:27 GMT Server: Apache/2.0.63 (Unix) DAV/2 X-Powered-By: Servlet/2.5 JSP/2.1 Transfer-Encoding: chunked Content-Type: multipart/related; type="application/xop+xml"; boundary="*uuid:0b4207bc-f374-4c94-a6c7-c6762711b57b*"; start="<[email protected]>"; start-info="text/xml" --uuid:0b4207bc-f374-4c94-a6c7-c6762711b57b Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"; Content-Transfer-Encoding: binary Content-ID: <[email protected]> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><ns2:processActionResponse xmlns:ns2="http://foo.com/comm";><ns2:CommActionResponse><ns2:CommId>999</ns2:CommId><ns2:CommTaskId>999</ns2:CommTaskId><ns2:CommStatus></ns2:CommStatus></ns2:CommActionResponse></ns2:processActionResponse></soap:Body></soap:Envelope> *--uuid:0b4207bc-f374-4c94-a6c7-c6762711b57b--* Is there a way to keep the uuid from going in the response when it's null? Could we use mtom-threshold of like 1 to force smaller docs or nulls (if thats what it does) to be inline? Thanks.... -- View this message in context: http://cxf.547215.n5.nabble.com/Disable-mtom-from-sending-uuid-when-DataHandler-is-null-tp5654978p5654978.html Sent from the cxf-user mailing list archive at Nabble.com.
