[
https://issues.apache.org/jira/browse/CAMEL-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damian updated CAMEL-4515:
--------------------------
Description:
Currently the Camel-Spring-WS component does not support the setting of SOAP
Headers and has issues getting them.
Change the component so that a Camel header "CamelSpringWebserviceSoapHeader"
can be populated with an intended SOAP Header for a request, and that this
Header is also populated from the SOAP Header on a response.
was:
SOAP Headers must be namespace qualified
(http://www.w3schools.com/soap/soap_header.asp), and when the Consumer extracts
the SOAP headers to populate the Exchange Headers it uses the QName.toString()
method. This results in a headers key like :
{http://mynamespace.url}MyHeaderKey
The SpringWebserviceConsumer should be modified to use the QName.getLocalPart()
method instead so that the Camel Header is (for example) "MyHeaderKey".
Patch Info: Patch Available
Summary: Spring-WS should populate Camel Header with the SOAP Header
(was: Spring-ws Consumer keeps SOAP Header namespace when populating Camel
Headers)
> Spring-WS should populate Camel Header with the SOAP Header
> -----------------------------------------------------------
>
> Key: CAMEL-4515
> URL: https://issues.apache.org/jira/browse/CAMEL-4515
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-ws
> Affects Versions: 2.8.1
> Reporter: Damian
> Priority: Minor
> Attachments: CAMEL-4515.patch
>
>
> Currently the Camel-Spring-WS component does not support the setting of SOAP
> Headers and has issues getting them.
> Change the component so that a Camel header "CamelSpringWebserviceSoapHeader"
> can be populated with an intended SOAP Header for a request, and that this
> Header is also populated from the SOAP Header on a response.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
