Return-Path: 
 <issues-return-19347-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
X-Original-To: apmail-cxf-issues-archive@www.apache.org
Delivered-To: apmail-cxf-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4C1DD97B0
	for <apmail-cxf-issues-archive@www.apache.org>;
 Thu,  8 Dec 2011 19:13:04 +0000 (UTC)
Received: (qmail 9559 invoked by uid 500); 8 Dec 2011 19:13:03 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 9533 invoked by uid 500); 8 Dec 2011 19:13:03 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 9503 invoked by uid 99); 8 Dec 2011 19:13:03 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2011 19:13:03 +0000
X-ASF-Spam-Status: No, hits=-2001.2 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2011 19:13:02 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 4E6E310759B
	for <issues@cxf.apache.org>; Thu,  8 Dec 2011 19:12:42 +0000 (UTC)
Date: Thu, 8 Dec 2011 19:12:42 +0000 (UTC)
From: "Daniel Kulp (Updated) (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: 
 <230585420.54400.1323371562322.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <414705988.27339.1321292153390.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CXF-3910) CXF "Thread-local" Request Context
 feature doesn't work with Dispatch Objects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Daniel Kulp updated CXF-3910:
-----------------------------

    Fix Version/s: NeedMoreInfo


We'll likely need a testcase for this.   I just ported our testcase for the=
 thread local request context to use dispatch clients in addition to the no=
rmal clients and the tests all pass and are doing what we expect.   Thus, i=
t looks like they are working fine.

               =20
> CXF "Thread-local" Request Context feature doesn't work with Dispatch Obj=
ects=20
> -------------------------------------------------------------------------=
-----
>
>                 Key: CXF-3910
>                 URL: https://issues.apache.org/jira/browse/CXF-3910
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.4.4
>         Environment: Ubuntu 11.10 64 bits
>            Reporter: Ben-Hur Carlos Vieira Langoni J=C3=BAnior
>             Fix For: NeedMoreInfo
>
>
> I am using the dispatch object for creating dynamic webservice clients :
>                 Service service=3DService.create(serviceName);=09
> =09=09service.addPort(portName, JMSSpecConstants.SOAP_JMS_SPECIFICATION_T=
RANSPORTID, address);
> =09=09
> =09=09Dispatch<SOAPMessage> dispatch =3D service.createDispatch(builder.b=
uild(),=20
> =09=09=09=09SOAPMessage.class, Mode.MESSAGE,
> =09=09=09=09enabledRequiredwsf);
> =09=09
> =09=09((BindingProvider)dispatch).getRequestContext().put("thread.local.r=
equest.context", true);=09
> I need to use the request context of each dispatch object with a thread l=
ocal scope. The use of "thread.local.request.context" in the request contex=
t of dispatch objects doesn't seem to affect its default behavior: The requ=
est context remains shared by all dispatch objects within the same classloa=
der. Is the thread-local request context feature supposed to work with Disp=
atch objects also, or only with conventional jax-ws proxies?     =20

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