[jboss-jira] [JBoss JIRA] (WFLY-4393) Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers

[Takashi Nishigaya (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Takashi Nishigaya updated WFLY-4393:
------------------------------------
    Description: 
CXF runtime does NOT propagate JAX-WS standard context value MessageContext.HTTP_REQUEST_HEADERS to the subsequent client-side SOAP handlers. For instance,

1. The first client handler puts the newly created HTTP request header map that contains the custom header 'foo' in the message context.
2. The second client handler can not refer to the custom header 'foo' added in the step 1. The HTTP request header map in the message context is null.

The weird thing is that the custom header added in the step 1 is correctly received by the server-side web services.
The both of Java SE default JAX-WS implementations and GlassFish correctly share HTTP_REQUEST_HEADERS map between handlers.

Please check the attached test case and compare the two test case. The method testHandlerChainOnServer() tests the case that the client is running on the container. On the other hand, testHandlerChainOnStandalone() tests the standalone client case.

In order to reproduce the issue:

$ mvm clean test -P wildly-managed (or -P wildly-remote)

Additionally, this behavior is the same in EAP 6.3.3.


> Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers
> ------------------------------------------------------------------------------------------
>
>                 Key: WFLY-4393
>                 URL: https://issues.jboss.org/browse/WFLY-4393
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web Services
>    Affects Versions: 8.2.0.Final
>            Reporter: Takashi Nishigaya
>            Assignee: Jason Greene
>
> CXF runtime does NOT propagate JAX-WS standard context value MessageContext.HTTP_REQUEST_HEADERS to the subsequent client-side SOAP handlers. For instance,
> 1. The first client handler puts the newly created HTTP request header map that contains the custom header 'foo' in the message context.
> 2. The second client handler can not refer to the custom header 'foo' added in the step 1. The HTTP request header map in the message context is null.
> The weird thing is that the custom header added in the step 1 is correctly received by the server-side web services.
> The both of Java SE default JAX-WS implementations and GlassFish correctly share HTTP_REQUEST_HEADERS map between handlers.
> Please check the attached test case and compare the two test case. The method testHandlerChainOnServer() tests the case that the client is running on the container. On the other hand, testHandlerChainOnStandalone() tests the standalone client case.
> In order to reproduce the issue:
> $ mvm clean test -P wildly-managed (or -P wildly-remote)
> Additionally, this behavior is the same in EAP 6.3.3.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)