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

Philippe CERY commented on CXF-4077:
------------------------------------

Please ignore the previous temporary solution as it is based on a 
WeakReference. I don't know how to delete an attached file.
                
> Body tag attributes from inbound message are lost in outbound message
> ---------------------------------------------------------------------
>
>                 Key: CXF-4077
>                 URL: https://issues.apache.org/jira/browse/CXF-4077
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime, Soap Binding
>    Affects Versions: 2.4.4, 2.5.1
>         Environment: jdk 1.6.0_30, tomcat 6.0.35, camel 2.9.0, cxf 2.5.1
>            Reporter: Philippe CERY
>             Fix For: NeedMoreInfo
>
>         Attachments: ReadHeadersInterceptor.java, 
> WriteBodyAttributesInterceptor.java, WriteBodyAttributesInterceptor.java
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Suppose you want to sign the whole soap body of your message. The Body tag 
> will have 2 attributes xmlns:wsu and wsu:Id added.
> I want my server to forward the message to another server without checking 
> signature and of course without modifying the signed part. 
> But the In interceptors (ReadHeadersInterceptor and StartBodyInterceptor) 
> ignore these attributes while parsing the inbound message and the 
> SoapOutInterceptor creates a new empty soap Body element.
> So, the signed part is considered as modified by the second server and the 
> message is rejected.
> If I want to sign any other part inside the body element, it works.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to