.NET can't parse CXF MTOM SoapFault response
--------------------------------------------

                 Key: CXF-1901
                 URL: https://issues.apache.org/jira/browse/CXF-1901
             Project: CXF
          Issue Type: Bug
    Affects Versions: 2.1.2
         Environment: CXF 2.1.2, Visual Studio 2005, WSE 3.0
            Reporter: Green Bar


I am  writing a CXF service that allows users to submit an XML MTOM attachment. 
If it does not validate, an exception is thrown. Our .NET client to this 
service initially failed to parse the SoapFault response because when MTOM was 
not being used on the response (after sending an MTOM request), .NET complained 
that the content-type received was text/xml and should have been 
multipart/related; type="application/xop+xml".

We added an interceptor to always force MTOM even on SOAP Faults, but now .NET 
does not even complain about an error even though one is definately coming back 
from the service. SOAP-ui and our test CXF client seems to get the response 
just fine. 

I have captured the request/response using Wireshark. Can someone tell me if 
there is some incompatibility with .NET and CXF regarding MTOM?

POST /ARM/ARM/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 
2.0.50727.832)
VsDebuggerCausalityData: 
uIDPo1FK6Ege1xJJlE8g800YAhEAAAAA1HpQBJKEb0qT0MJzZZvKMnaK7XB+PVNNnqhZc/qYhSQACAAA
SOAPAction: ""
Content-Type: multipart/related; type="application/xop+xml"; 
boundary=--MIMEBoundary633614736135473680; start="<[EMAIL PROTECTED]>"; 
start-info="text/xml; charset=utf-8"
Authorization: Basic YXJtVXNlcjphcm1QYXNz
Host: localhost:8082
Content-Length: 1565
Expect: 100-continue

HTTP/1.1 100 Continue


----MIMEBoundary633614736135473680
content-id: <[EMAIL PROTECTED]>
content-type: application/xop+xml; charset=utf-8; type="text/xml; charset=utf-8"
content-transfer-encoding: binary

<soap:Envelope xmlns:xop="http://www.w3.org/2004/08/xop/include"; 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; 
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";
 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";><soap:Header><wsa:Action></wsa:Action><wsa:MessageID>urn:uuid:facd98ff-af0d-4c80-a68c-ca384275ab9c</wsa:MessageID><wsa:ReplyTo><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo><wsa:To>http://
 localhost:8082/ARM/ARM/</wsa:To><wsse:Security><wsu:Timestamp 
wsu:Id="Timestamp-22a6a1e3-217e-48e3-b68d-9224b7064b3b"><wsu:Created>2008-11-05T14:20:13Z</wsu:Created><wsu:Expires>2008-11-05T14:25:13Z</wsu:Expires></wsu:Timestamp></wsse:Security></soap:Header><soap:Body><postSubmission
 
xmlns="http://service.arm.hud.gov/";><submissionHeader><agcHcsId>1</agcHcsId><agcName>test</agcName><subType>test</subType><submissionId>0</submissionId><systemName>test</systemName></submissionHeader><agcType>test</agcType><submissionData>[EMAIL
 PROTECTED]</submissionData></postSubmission></soap:Body></soap:Envelope>
----MIMEBoundary633614736135473680--


HTTP/1.1 200 OK
Content-Type: multipart/related; type="application/xop+xml"; 
boundary="----=_Part_0_30296714.1225894814362"; start="<[EMAIL PROTECTED]>"; 
start-info="text/xml"
Content-Length: 539
Server: Jetty(6.1.9)


------=_Part_0_30296714.1225894814362
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><soap:Fault><faultcode
 
xmlns:ns1="http://www.w3.org/2003/05/soap-envelope";>ns1:Receiver</faultcode><faultstring>cvc-elt.1:
 Cannot find the declaration of element 'databag'. 
</faultstring></soap:Fault></soap:Body></soap:Envelope>
------=_Part_0_30296714.1225894814362--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to