[jira] Resolved: (CXF-470) Request and Response contexts are the no thread-local objects of the JaxWsClientProxy

["willem Jiang (JIRA)" <ji...@apache.org>]

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

willem Jiang resolved CXF-470.
------------------------------

    Resolution: Fixed

This issue has been resloved in the revision 520299.

> Request and Response contexts are the no thread-local objects of the JaxWsClientProxy
> -------------------------------------------------------------------------------------
>
>                 Key: CXF-470
>                 URL: https://issues.apache.org/jira/browse/CXF-470
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.0-RC
>            Reporter: willem Jiang
>         Assigned To: willem Jiang
>             Fix For: 2.0-RC
>
>
> The CXF documentation at http://cwiki.apache.org/CXF20DOC/developing- a-consumer.html illustrates a pattern for implementing a CXF client.   Under the section "Setting a request context" and "Reading a response  context", the following code is presented:
> {{{
> // Set request context property.
> java.util.Map<String, Object> requestContext =
>   ((javax.xml.ws.BindingProvider)port).getRequestContext();
> requestContext.put(ContextPropertyName, PropertyValue);
> // Invoke an operation.
> port.SomeOperation();
> // Read response context property.
> java.util.Map<String, Object> responseContext =
>   ((javax.xml.ws.BindingProvider)port).getResponseContext();
> PropertyType propValue = (PropertyType) responseContext.get (ContextPropertyName);
> }}}
> The port is the instance of  JaxWsClientProxy which implements the BindingProvider interface.
> The RequestContext and the ResponseContext should be thread safe for multi-thread share the same client proxy to gain better scability.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.