We have a fairly simple WS, implemented using annotations. We would like to be able to call this from clients as MTOM / XOP support, or not. Right now, this is annotating just @MTOM.
It accepts a request containing (among others) a base64 base element, and serves to respond with a single logical element.
The call is not a problem, either with ours without MTOM - it works. Only the answer, even if it does not contain any MTOMs: capable elements have headers declaring this as a MTOM message that pinches the client without MTOM.
<tran:headers xsi:type="http:HttpResponseHeaders" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<tran:user-header name="X-Powered-By" value="Servlet/2.5 JSP/2.1"/>
<http:Content-Type>
multipart/related;start="<rootpart*c3e56707-113c-47f9-b02c-2a3234766dc4@example.jaxws.sun.com>";type="application/xop+xml";boundary="uuid:c3e56707-113c-47f9-b02c-2a3234766dc4";start-info="text/xml"
</http:Content-Type>
<http:Date>Tue, 11 May 2010 07:27:51 GMT</http:Date>
<http:Transfer-Encoding>chunked</http:Transfer-Encoding>
</tran:headers>
Does anyone know how to make a service always respond with a response other than MTOM while still accepting MTOM and non-MTOM requests?
The service starts on the WebLogic 10.3 server ...
Regards, Lars