cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Resolved: (CXF-1901) .NET can't parse CXF MTOM SoapFault response
Date Thu, 20 Nov 2008 21:48:46 GMT


Daniel Kulp resolved CXF-1901.

       Resolution: Won't Fix
    Fix Version/s: Invalid

Seems to be a setup issue with the .NET client.   Thus, marking it "won't fix"

> .NET can't parse CXF MTOM SoapFault response
> --------------------------------------------
>                 Key: CXF-1901
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.1.2
>         Environment: CXF 2.1.2, Visual Studio 2005, WSE 3.0
>            Reporter: Green Bar
>             Fix For: Invalid
> 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?
> 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="<>"; 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: <>
> content-type: application/xop+xml; charset=utf-8; type="text/xml; charset=utf-8"
> content-transfer-encoding: binary
> <soap:Envelope xmlns:xop="" xmlns:soap=""
xmlns:xsi="" xmlns:xsd=""
xmlns:wsa="" xmlns:wsse=""
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
> ----MIMEBoundary633614736135473680--
> HTTP/1.1 200 OK
> Content-Type: multipart/related; type="application/xop+xml"; boundary="----=_Part_0_30296714.1225894814362";
start="<>"; 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: <>
> <soap:Envelope xmlns:soap=""><soap:Body><soap:Fault><faultcode
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.

View raw message