title: How do I mark SOAP service 'MTOM enabled'
body: <p>This is not Java specific question, but let's have an example in Java: It is a standard practice in the Java world to add <code>xmime:expectedContentTypes="*/*</code> to base64 elements to enable MTOM processing on the server side - it results in the <code>@XmlMimeType</code> annotation, use of <code>DataHandler</code>s instead of byte arrays etc. While this description is of course greatly simplified, <code>xmime:expectedContentTypes="*/*</code> is usually recognized as 'MTOM ready' by the developers (and more importantly also by the implementing libraries) when seen in the schema. From what I've gathered from the examples, the situation is the same in the C# world.</p>
  
  <p>It does however make no sense to me - the attribute specifies what kind of data we might actually expect in the XML, not that it can be used together with MTOM. I have also not found any direct connection between expected content type and MTOM in any RFC or similar document for SOAP 1.1.</p>
  
  <p>My question can be phrased in two ways:</p>
  
  <ol>
  <li>How does the service make clear that it accepts / serves binary data as MTOM attachments in the request / response?</li>
  <li>How does the client correctly recognize that the binary data can be sent / obtained by using MTOM attachments for the given service?</li>
  </ol>