Re: Proposed Final Draft
it is very late for changing anything..
We are not saying that on Java EE environment ClientBuilder#executorService and #scheduledExecutorService have no effect - but it might sound that way.
The "default" for Java SE is NOT ForkJoinPool#commonPool, since
it is not meant for I/O operations. On Java SE, the default is
intentionally left as implementation specific.
And I'm not sure what you mean by "what about Future Objects returned from ..." - if there is any need for starting a thread, it should be done on the executor service provided in the client builder. Note that the javadoc for ClientBuilder#executorService mentions:
* Provided executor service will be used for executing asynchronous tasks.
And Invocation#buildGet() (and others):
* Submit the request for an asynchronous invocation and receive a future * response back.
Which seem to imply what I wrote..
It might be still possible to tweak the javadoc, I'll wait for your reaction - whether this makes sense or not and then will inquire about possible javadoc adjustment.
Thanks and regards,
On 07/07/2017 00:35, Andy McCright wrote: