cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk Rudolph (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-3514) Interaction of JAXWS Handler and WSS4JInInterceptor breaks SOAP Message
Date Fri, 13 May 2011 14:21:47 GMT

    [ https://issues.apache.org/jira/browse/CXF-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033052#comment-13033052
] 

Dirk Rudolph commented on CXF-3514:
-----------------------------------

I fixed this issue by adding the WSS4JInInterceptor before the SOAPHandlerInInterceptor but
this is only a dirty work around.
In my project I have to use the SOAPHandler to start/stop the Seam lifecycle that is also
needed by the PasswordCallback.

> 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
>              Labels: security
>         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

Mime
View raw message