[jira] [Updated] (CXF-4289) Coping Request SOAP Headers to Fault response

["Daniel Kulp (JIRA)" <ji...@apache.org>]

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

Daniel Kulp updated CXF-4289:
-----------------------------

    Fix Version/s: 2.7.2
                   2.6.5
    
> Coping Request SOAP Headers to Fault response
> ---------------------------------------------
>
>                 Key: CXF-4289
>                 URL: https://issues.apache.org/jira/browse/CXF-4289
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Andrei Shakirin
>            Assignee: Ulhas Bhole
>            Priority: Minor
>             Fix For: 2.6.5, 2.7.2
>
>         Attachments: JAXWSMethodInvoker.patch
>
>
> Hi,
> Actually JAXWSMethodInvoker and AbstractJAXWSMethodInvoker contain code to copy request soap headers (except security one) to SOAP Fault: AbstractJAXWSMethodInvoker.updateHeader().
> I see some use cases when it is not really desired:
> 1) Request SOAP headers contains some labelling information about request elements and they make sense only with request
> 2) Request SOAP headers extending request elements with meta-information
> If request headers are copied into fault response, they can be invalid in response context and cause undesired effects:
> a) it makes response processing on the client side more difficult, especially if processing interceptor is called before incoming fault message is recognized and placed into exchange.getInFaultMessage()
> b) response fault message has larger size
> Proposal is to define context property that give user the possibility to switch-off coping request headers into fault response.
> Patch is attached.
> Regards,
> Andrei.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira