[CXF-2101] Cannot add headers to request from Dispatch client in async mode -- ThreadLocal issue

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.4
• Fix Version/s: 2.1.5
• Component/s: JAX-WS Runtime

Environment

JDK 1.6.0_10

• Estimated Complexity: Advanced
• Assignee: Daniel Kulp
• Reporter: Andrew Clegg
• Created: 10/Mar/09 17:59
• Updated: 24/Apr/09 21:17
• Resolved: 12/Mar/09 19:37

Description

org.apache.cxf.jaxws.DispatchImpl extends org.apache.cxf.jaxws.BindingProviderImpl, which has a requestContext field:

protected ThreadLocal <Map<String, Object>> requestContext =
new ThreadLocal<Map<String, Object>>();

Because the request context is in a ThreadLocal, changes made to it are not visible when you invoke the service via DispatchImpl's invokeAsync method.

For example:

dispatch.getRequestContext().put(
BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.TRUE );
dispatch.getRequestContext().put(
BindingProvider.SOAPACTION_URI_PROPERTY, "uri:myAction" );

// If you call it this way, no SOAPAction header, verified by Wireshark:
Response<StreamSource> response = dispatch.invokeAsync( request );

// But if you call it this way, you get the header
StreamSource result = dispatch.invoke( request );

I can package up a test case if anyone thinks it would help fix this. Personally I know very little about CXF's internals, or the JAX-WS specs, but I can do whatever necessary to help.

Issue Links

• relates to: CXF-1907 Refactor JAX-WS Dispatch clients....