mimeType attribute in MTOM/XOP attachments
------------------------------------------
Key: XFIRE-1061
URL: http://jira.codehaus.org/browse/XFIRE-1061
Project: XFire
Issue Type: Bug
Affects Versions: 1.2.6
Reporter: Zachary Jones
Assignee: Dan Diephouse
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://milkaholics.anonymous.hiphopanonymous";
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://milkaholics.anonymous.hiphopanonymous";
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://milkaholics.anonymous.hiphopanonymous";
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>
The mimeType attribute is not in the http://www.w3.org/2004/11/xmlmime 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.
Also, why not upgrade to the 2005 xmime schema?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
