You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2014/12/21 09:04:13 UTC

[jira] [Updated] (CAMEL-8162) camel-spring-ws removes WSHandlerResult.

     [ https://issues.apache.org/jira/browse/CAMEL-8162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-8162:
-------------------------------
    Estimated Complexity: Novice  (was: Unknown)

> 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
>            Priority: Minor
>             Fix For: 2.15.0
>
>
> 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.4#6332)