[xfire-user] xmime namespace and mimeType attribute in

[Jones, Zack (SAIC)]

I am using XFire stubs to submit binary data as an MTOM/XOP attachment. 

In version 1.2.5, XFire would send an MTOM/XOP attachment similar to the 
following:

<?xml version="1.0" encoding="UTF-8"?><jdn:submitUploadTransaction 
xmlns:jdn="http://jdnets.jopes.ap.necc.disa.mil"; 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
  <jdn:upload>
    <inc:Include xmlns:inc="http://www.w3.org/2004/08/xop/include"; 
href="cid:1183737071644"/>
  </jdn:upload>
</jdn:submitUploadTransaction>

Contrast this to the way SOAP-ui sends the same attachment (notice the 
contentType attribute in the upload element):

<?xml version="1.0" encoding="UTF-8"?><jdn:submitUploadTransaction 
xmlns:jdn="http://jdnets.jopes.ap.necc.disa.mil"; 
xmlns:xm="http://www.w3.org/2005/05/xmlmime"; 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
  <jdn:upload xm:contentType="text/xml">
    <inc:Include xmlns:inc="http://www.w3.org/2004/08/xop/include"; 
href="cid:1183737071644"/>
   </jdn:upload>
</jdn:submitUploadTransaction>


In version 1.2.6, XFire sends the following (instead of contentType, it is 
using mimeType with the 2004 xmime namespace):

<?xml version="1.0" encoding="UTF-8"?><jdn:submitUploadTransaction 
xmlns:jdn="http://jdnets.jopes.ap.necc.disa.mil"; 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
  <jdn:upload xmlns:ns1="http://www.w3.org/2004/11/xmlmime"; 
ns1:mimeType="text/plain">
    <inc:Include xmlns:inc="http://www.w3.org/2004/08/xop/include"; 
href="cid:1183737071644"/>
  </jdn:upload>
</jdn:submitUploadTransaction>


Question 1: What is mimeType is relation to the 
http://www.w3.org/2004/11/xmlmime schema?. It does not exist in that schema.
Question 2: Why not upgrade to the 2005 xmime schema.

My concern is this...we are validating the xml in the SOAP body against our web 
service schemas.  Prior to the 1.2.6 change, we could validate fine, as we had 
the contentType attribute specified as optional. Now validation fails because 
we are not expecting the mimeType attribute from the 
http://www.w3.org/2004/11/xmlmime namespace. 

We can live with using the http://www.w3.org/2004/11/xmlmime namespace, but I 
don't understand the use of the mimeType attribute.

Am I missing something here, or is this a legitimate concern?

Thanks in advance,
Zack Jones