>From the documentation, it says that: "A single client doing multiple invocations without changing the current URI or headers is thread-safe."
Now, what happens if we have @HeaderParam in the API of the service? Does that count as "changing headers", thereby making the client proxy not thread-safe? Also, there is mention of: "Final option is to use a 'threadSafe' boolean property when creating proxies or web clients (either from Spring or programmatically), see this test <http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxrs/src/test/java/org/apache/cxf/systest/jaxrs/JAXRSMultithreadedClientTest.java> for more details. Thread-safe clients created this way keep their state in a thread-local storage." I don't see any setting of a "threadSafe" boolean property in that test: http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxrs/src/test/java/org/apache/cxf/systest/jaxrs/JAXRSMultithreadedClientTest.java Where would I set that "threadSafe" property in order to force the proxy to use ThreadLocal storage for its state? Has anyone already implemented a dynamic proxy that creates a new proxy (WebClient.fromClient or JAXRSClientFactoryBean.fromClient) internally for every call? Thanks, James
