Hi Sergey, 2017-10-07 19:01 GMT+02:00 Sergey Beryozkin <[email protected]>:
> Hi Romain > > Was the idea it would be passed via one of rx() methods ? > more through Client/WebTarget/... (Configurations) properties without cxf imports required > > Though we can def start with 1. for sure, what property name do you > suggest ? > org.apache.cxf.jaxrs.client.rx.executor or anything matching cxf naming convention > > The look up (3.), would it require a non-SE dependency ? > No, lookup java:comp/DefaultManagedExecutorService and cast it to ExecutorService > > Cheers, Sergey > On 07/10/17 17:18, Romain Manni-Bucau wrote: > >> Hi guys, >> >> seems CompletionStageRxInvokerImpl doesn't support a user defined executor >> nor a default EE managed executor. Would it be an option to default to >> these impl instead of relying on the JVM implementation which makes it >> hard >> to tune? >> >> High level algorithm would be: >> >> 1. if user defined a custom executor in properties use it >> 2. if user defined a pool configuration (min/max/core/queue sizes) then >> create a new pool >> 3. if default managed executor service (from EE) exists then use it - >> simple lookup should be good >> 4. use forkjoin default pool like today >> >> wdyt? >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <https://rmannibucau.metawerx.net/> | Old Blog >> <http://rmannibucau.wordpress.com> | Github < >> https://github.com/rmannibucau> | >> LinkedIn <https://www.linkedin.com/in/rmannibucau> >> >>
