You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by GitBox <gi...@apache.org> on 2018/01/20 01:14:13 UTC

[GitHub] johnament commented on issue #368: Ensure that the JAX-RS CompletionStage uses the correct ExecutorService

johnament commented on issue #368: Ensure that the JAX-RS CompletionStage uses the correct ExecutorService
URL: https://github.com/apache/cxf/pull/368#issuecomment-359132180
 
 
   @andymc12 I kind of agree with @reta (but for a slightly different reason I think..), since we're using the static method that passes in the `ExecutorService`, the same `ExecutorService` will be used for the remaining invocations of the methods here, while CXF is in control.  By definition, a user shouldn't be using `supplyAsync` that doesn't take an `ExecutorService` afterwards; if this is what they're after.
   
   What we do probably have to make happen is a way to get the `ExecutorService` from the underlying client, if the user doesn't have access to it already (maybe they can get via the `Configuration` class?)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services