Re: All CXF repos moved to gitbox....

2017-10-07 Thread Andriy Redko
Hey Dennis, I've just ported a few fixes to 3.1.x branch and noticed that this branch is not being built on Jenkins since Sep, 8th (https://builds.apache.org/job/CXF-3.1.x/). I am wondering if we reconfigured this job to use Gitbox? Or there is another one for 3.1.x? Thanks. Best Regards,

Re: [JAXRS][CLIENT] rx() executor

2017-10-07 Thread Romain Manni-Bucau
Hi Sergey, 2017-10-07 19:01 GMT+02:00 Sergey Beryozkin : > 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,

Re: [JAXRS][CLIENT] rx() executor

2017-10-07 Thread Sergey Beryozkin
Hi Romain Was the idea it would be passed via one of rx() methods ? Though we can def start with 1. for sure, what property name do you suggest ? The look up (3.), would it require a non-SE dependency ? Cheers, Sergey On 07/10/17 17:18, Romain Manni-Bucau wrote: Hi guys, seems

[JAXRS][CLIENT] rx() executor

2017-10-07 Thread Romain Manni-Bucau
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

Re: Swagger2Feature bug caused by removal of isScan() check

2017-10-07 Thread Sergey Beryozkin
Hi Dennis Thanks very much, my fault really as I did not see a point in keeping this property in 3.2.x and indeed, as you imply, all tests were/are still passing, but I guess more preparation should've gone into it. Setting a scan to true did never work in OSGI as far as I know, may be in

Re: Swagger2Feature bug caused by removal of isScan() check

2017-10-07 Thread Dennis Kieselhorst
Hi Taylor! > This causes the subsequent code (line 196): > > BeanConfig beanConfig = appInfo == null > ? new BeanConfig() > : new ApplicationBeanConfig(appInfo.getProvider()); > > …to always instantiate an ApplicationBeanConfig object. Our production code > relied on the BeanConfig’s