cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (Updated) (JIRA)" <>
Subject [jira] [Updated] (CXF-3910) CXF "Thread-local" Request Context feature doesn't work with Dispatch Objects
Date Thu, 08 Dec 2011 19:12:42 GMT


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 normal clients and the tests all pass and
are doing what we expect.   Thus, it looks like they are working fine.

> CXF "Thread-local" Request Context feature doesn't work with Dispatch Objects 
> ------------------------------------------------------------------------------
>                 Key: CXF-3910
>                 URL:
>             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Ășnior
>             Fix For: NeedMoreInfo
> I am using the dispatch object for creating dynamic webservice clients :
>                 Service service=Service.create(serviceName);	
> 		service.addPort(portName, JMSSpecConstants.SOAP_JMS_SPECIFICATION_TRANSPORTID, address);
> 		Dispatch<SOAPMessage> dispatch = service.createDispatch(, 
> 				SOAPMessage.class, Mode.MESSAGE,
> 				enabledRequiredwsf);
> 		((BindingProvider)dispatch).getRequestContext().put("thread.local.request.context",
> I need to use the request context of each dispatch object with a thread local scope.
The use of "thread.local.request.context" in the request context of dispatch objects doesn't
seem to affect its default behavior: The request context remains shared by all dispatch objects
within the same classloader. Is the thread-local request context feature supposed to work
with Dispatch objects also, or only with conventional jax-ws proxies?      

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message