camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Siano (JIRA)" <>
Subject [jira] [Updated] (CAMEL-8663) Namespaces defined on the SOAP envelope get lost in PAYLOAD mode
Date Mon, 04 May 2015 12:48:06 GMT


Stephan Siano updated CAMEL-8663:
    Attachment:     (was: 0001-CAMEL-8663-Namespaces-defined-on-SOAP-envelope-lost-.patch)

> Namespaces defined on the SOAP envelope get lost in PAYLOAD mode
> ----------------------------------------------------------------
>                 Key: CAMEL-8663
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf
>            Reporter: Stephan Siano
>         Attachments: 0001-CAMEL-8663-Namespaces-defined-on-SOAP-envelope-lost-.patch
> If a request message is send to a CXF consumer or a response is returned to the CXF provider
that contains namespace definions at the SOAP envelope and the Camel-CXF endpoint is configured
in PAYLOAD mode the namespace definition gets lost unless streaming is disabled.
> If the resulting CxfPayload is then converted e.g. to String that String will contain
invalid XML (because some namespace definition is missing).
> For non-streaming mode (system property org.apache.camel.component.cxf.streaming is set
to false) there are special precautions met to set these envelope namespaces on the first
DOM element of the payload but this coding is missing for StAX.
> The messages in question look like that:
> <soap:Envelope xmlns:soap="" xmlns:xsi=""
>   <soap:Body>
>     <ns2:getTokenResponse xmlns:ns2="">
>       <return xsi:type="xs:string">Return Value</return>
>     </ns2:getTokenResponse>
>   </soap:Body>
> </soap:Envelope>
> If the CxfPayload is converted to String it will lack the definition for the xsi namespace
prefix (and further XML parsing will fail).

This message was sent by Atlassian JIRA

View raw message