[
https://issues.apache.org/jira/browse/CXF-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040115#comment-13040115
]
Dirk Rudolph commented on CXF-3514:
-----------------------------------
I tested your changes against the java_first_spring_support example and my
current project and it works for both.
The last unresolved question remaining in my mind is, why the
WSS4JInInterceptor can't be run after the SOAPHandlerInterceptor? When I set
the Phase for a custom WSS4JInInterceptor to USER_PROTOCOL (for example) the
same problems occure.
The background of my question is this. I use a jaxws handler to start an
application lifecycle (seam framework), which is already needed in the
PasswordCallback invoked by the WSS4JInInterceptor.
> 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
