[
https://issues.apache.org/jira/browse/CAMEL-9103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bjørn Hilstad updated CAMEL-9103:
---------------------------------
Attachment: (was: camel-jboss-web.7z)
> camel-cxf does not handle soapfaults with ws-addressing headers in async mode
> -----------------------------------------------------------------------------
>
> Key: CAMEL-9103
> URL: https://issues.apache.org/jira/browse/CAMEL-9103
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.15.3
> Reporter: Bjørn Hilstad
> Priority: Minor
>
> I am invoking a SOAP 1.1 webservice with WS-Addressing using camel-cxf. When
> the webservice returns a soapfault that includes a ws-addressing header
> (<wsa:Action>http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action>)
> which I believe is allowed per spec (ws-addressing) I can see in logs that
> cxf processes the response but the response never reaches Camel (would be
> handled by the DefaultErrorHandler). The thread just hangs forever.
> I have been able to get the same test to work if I configure the camel
> endpoint for cxf to use synchronous=true.
> I am attaching a maven project that contains a test that reproduces the
> issue. The test uses wiremock as a stub to return the response.
> If the endpoint in the camelcontext is changed to use synchronous=true the
> test succeeds (it gets the soapfault that is expected).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
