title: How to correctly share JAX-RS 2.0 client
body: <p>To give a little context to my issue...</p>
  
  <p>I have a Java EE web application (as a UI / client) that accesses services for data / business logic via a REST interface using the JAX-RS 2.0 client API (Resteasy implementation).</p>
  
  <p>Currently I inject a new JAXRS Client instance per request using a RequestScoped CDI managed bean, the thinking being that the client app may call multiple backend resources per request and I reuse the same JAXRS Client for the whole request (although I read somewhere this may not be correct as I am potentially changing the URI for each invocation)</p>
  
  <p>The documentation for JAXRS Client seems to suggest that the client is a potentially expensive operation and the app should limit the amount of connections it creates.  It also seems to contradict itself and suggest the client should be closed once all the requests to a particular WebTarget are finished.</p>
  
  <p>The client application could potentially support thousands of simultaneous users  so creating and destroying thousands of 'expensive clients' does not seem to be the correct approach so am thinking a shared client pool is more appropriate but there doesn't seem to be any information on how this should be achieved.</p>
  
  <p>All examples appear to show creating a new client for the request and a) closing it after or b) not closing it but not really explaining what happens on a second request.</p>
  
  <p>Can you help provide some answers on how you think this would be solved or information on what the best practice for this approach is.</p>
  
  <p>Thanks.</p>