[
https://issues.apache.org/jira/browse/CAMEL-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006390#comment-14006390
]
Lucas Smith edited comment on CAMEL-4515 at 5/22/14 8:00 PM:
-------------------------------------------------------------
Guys, the lack of the possibility to inject a custom XmlConverter (or even a
custom TransformerFactory into XmlConverter) is a big limitation. I cannot
create a SOAP header with multiple nodes:
{code}
<soap-env:Header>
<MyFirstHeader>...</MyFirstHeader>
<MySecondHeader>...</MySecondHeader>
</soap-env:Header>
{code}
I can only have 'a one-child-node' SOAP header. The current implementation just
performs identity transformation which blindly copies the content of Camel's
SOAP header into <soap-env:Header>. It can be resolved with a custom
Transformer with XSLT. However, I cannot set that custom Transformer because I
cannot inject a custom TransformerFactory because XmlConverter is 100% static.
was (Author: lucassmith):
Guys, the lack of the possibility to inject a custom XmlConverter (or even a
custom TransformerFactory into XmlConverter) is a big limitation. I cannot
create a SOAP header with multiple nodes:
{code}
<soap-env:Header>
<MyFirstHeader>...</MyFirstHeader>
<MySecondHeader>...<MyFirstHeader>
</soap-env:Header>
{code}
I can only have 'a one-child-node' SOAP header. The current implementation just
performs identity transformation which blindly copies the content of Camel's
SOAP header into <soap-env:Header>. It can be resolved with a custom
Transformer with XSLT. However, I cannot set that custom Transformer because I
cannot inject a custom TransformerFactory because XmlConverter is 100% static.
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.11.1, 2.12.0
>
> Attachments: CAMEL-4515.1.patch, CAMEL-4515.2.patch
>
>
> Currently the Camel-Spring-WS component does not support the setting of SOAP
> Headers and has issues getting them. The current issue getting the SOAP
> Headers when receiving a message is that the resulting header key includes
> the namespace.
> 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 was sent by Atlassian JIRA
(v6.2#6252)
