Ray is correct to point this out. Using the ClientBuilder service avoids the lifecycle issues that you were seeing, and gives you a way to set up clients using different sets of extensions and configurations.
Unfortunately the “classic” usage of the JAX-RS API with its prevalence of static methods is not always friendly in a system with dynamic modules. Tim Sent from my iPhone On 24 Nov 2018, at 21:16, t...@quarendon.net wrote: >> Did you notice that the JAX-RS Whiteboard provides a ClientBuilder >> (prototype scoped) service? >> >> e.g. >> @Reference >> ClientBuilder clientBuilder; >> > > Ah, no, I hadn't. I had read the words, but obviously not understood the > significance. > Thanks for the pointer.
