[
https://issues.apache.org/jira/browse/CXF-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040185#comment-13040185
]
Daniel Kulp commented on CXF-3514:
----------------------------------
Per JAX-WS spec, we have to fill in the operation name in the context when
passing into the JAX-WS handlers. In many cases, we need to have the body
decrypted in order to figure out the operation that is being invoked which is
the primary reason for having the WSS4J stuff run before hand.
> Interaction of JAXWS Handler and WSS4JInInterceptor breaks SOAP Message
> -----------------------------------------------------------------------
>
> Key: CXF-3514
> URL: https://issues.apache.org/jira/browse/CXF-3514
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, WS-* Components
> Affects Versions: 2.4
> Environment: The java_first_spring_support example.
> Reporter: Dirk Rudolph
> Assignee: Daniel Kulp
> Labels: security
> Fix For: 2.4.1
>
> Attachments: SOAPRequestHandler.java, UTPasswordCallback.java,
> beans.xml, pom.xml
>
>
> Adding a JAXWS Handler (SOAPHandler implementation) to an endpoint
> configuration that uses the WSS4JInInterceptor breaks the recieved
> SOAPMessage. This results in missing binding or parameter information while
> invoking the webservice methods.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
