[
https://issues.apache.org/jira/browse/CXF-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben-Hur Carlos Vieira Langoni Júnior updated CXF-3910:
------------------------------------------------------
Description:
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(builder.build(),
SOAPMessage.class, Mode.MESSAGE,
enabledRequiredwsf);
((BindingProvider)dispatch).getRequestContext().put("thread.local.request.context",
true);
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?
was:
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(builder.build(),
SOAPMessage.class, Mode.MESSAGE,
enabledRequiredwsf);
((BindingProvider)dispatch).getRequestContext().put("thread.local.request.context",
true); }}
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?
> CXF "Thread-local" Request Context feature doesn't work with Dispatch Objects
> ------------------------------------------------------------------------------
>
> 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únior
>
> 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(builder.build(),
> SOAPMessage.class, Mode.MESSAGE,
> enabledRequiredwsf);
>
>
> ((BindingProvider)dispatch).getRequestContext().put("thread.local.request.context",
> true);
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
