cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (CXF-3910) CXF "Thread-local" Request Context feature doesn't work with Dispatch Objects
Date Wed, 18 Jan 2012 20:22:40 GMT


Daniel Kulp resolved CXF-3910.

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: NeedMoreInfo)
         Assignee: Daniel Kulp

Test case in our system tests does not show the problem and request for a test showing the
issue unanswered for over a month.
> 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
>            Assignee: Daniel Kulp
>             Fix For: Invalid
> 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