[
https://issues.apache.org/jira/browse/CAMEL-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867889#comment-15867889
]
onder sezgin commented on CAMEL-8162:
-------------------------------------
this is not camel-spring-ws component issue. This is how you should implement
using wss4j via
webServiceTemplate(org.springframework.ws.client.core.WebServiceTemplate)
normally wss4j removes security headers when returning to client unless
removeSecurityHeader is specified as false in the interceptor.
this should not be issue. i am going to set this issue as invalid after
providing some unit tests.
> camel-spring-ws removes WSHandlerResult.
> ----------------------------------------
>
> Key: CAMEL-8162
> URL: https://issues.apache.org/jira/browse/CAMEL-8162
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-ws
> Affects Versions: 2.14.0
> Reporter: Jimmy Selgen Nielsen
> Assignee: onder sezgin
> Priority: Minor
> Fix For: Future
>
>
> When using camel-spring-ws with WS-Security and Wss4jSecurityInterceptor,
> camel-spring-ws removes the list of WSHandlerResult when it creates the
> exchange from the messageContext.
> I'm trying to extract an X.509 certificate from the Soap header.
> Wss4jSecurityInterceptor removes the Security header when it successfully
> validates a message, and stores the information within the MessageContext in
> a List<WSHandlerResult>.
> I currently get around this by overriding Wss4jSecurityInterceptor so that it
> no longer deletes the Security header, but the information is essentially
> lost when Camel takes over, and it should be corrected.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
