Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Thu, 23 Jul 2015 02:48:04 +0000 (UTC)
From: "Jim Ma (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12848445.1437619633000.267507.1437619684521@Atlassian.JIRA>
In-Reply-To: <JIRA.12848445.1437619633000@Atlassian.JIRA>
References: <JIRA.12848445.1437619633000@Atlassian.JIRA>
 <JIRA.12848445.1437619633348@arcas>
Subject: [jira] [Created] (CXF-6506) Client-side message context value
 HTTP_REQUEST_HEADERS is not shared between SOAP handlers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jim Ma created CXF-6506:
---------------------------

             Summary: Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers
                 Key: CXF-6506
                 URL: https://issues.apache.org/jira/browse/CXF-6506
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
    Affects Versions: 3.1.1, 3.0.5
            Reporter: Jim Ma
            Assignee: Jim Ma
             Fix For: 3.0.6, 3.1.2


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.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)