Re: CXF release 3.1.7

> On Jul 29, 2016, at 12:24 PM, Adam Crevel wrote: > > Hi Dan - were the builds able to be created? On a related note, do you have > a rough idea when we will see CXF 3.1.7 on Maven Central (if that is not > covered under what you meant by creating the builds)? The vote

Re: CXF release 3.1.7

Hi Dan - were the builds able to be created? On a related note, do you have a rough idea when we will see CXF 3.1.7 on Maven Central (if that is not covered under what you meant by creating the builds)? Adam On Mon, Jul 25, 2016, 09:37 Adam Crevel wrote: > That's

RE: Fault chains in cxf clients

Hi Jason, You could find pretty nice description here: https://access.redhat.com/documentation/en-US/Fuse_ESB_Enterprise/7.0/html-single/Developing_Apache_CXF_Interceptors/index.html The fault chain on client side is working in following way: a) outgoing if exception happens in client

RE: Error during WebSocket handshake: Unexpected response code

Ok, I will test (starting from the second week of August) and let you know. Thanks! :) Regards, JP -Message d'origine- De : Aki Yoshida [mailto:elak...@gmail.com] Envoyé : vendredi 29 juillet 2016 15:34 À : CLEMENT Jean-Philippe Cc : users@cxf.apache.org Objet : Re: Error during

Re: IndexOutOfBoundsException when "Authorization" header is empty String

I suppose if Authorization is empty then one option is to assume the blank credentials are provided. Is there some text around supporting it ? We might be able to fix it for 3.1.8 I guess for now you can register a servlet filter to deal with the empty header. Cheers, Sergey On 29/07/16

Re: Error during WebSocket handshake: Unexpected response code

or wait a few days and try cxf-3.1.7's feature. 2016-07-29 15:14 GMT+02:00 Aki Yoshida : > My mistake cxf-3.1.x uses atmosphere 2.3.x. > > But cxf-3.1.6 doesn't come with the jax_rs_websocket_osgi sample, so > there is no mvn:org.apache.cxf.samples/jax_rs_websocket_osgi/3.1.6

Re: Error during WebSocket handshake: Unexpected response code

My mistake cxf-3.1.x uses atmosphere 2.3.x. But cxf-3.1.6 doesn't come with the jax_rs_websocket_osgi sample, so there is no mvn:org.apache.cxf.samples/jax_rs_websocket_osgi/3.1.6 unless you have taken the 3.1.x-SNAPSHOT version and renamed it and built it locally. Please try the whole procedure

RE: Error during WebSocket handshake: Unexpected response code

Thank you Aki for your support. I strictly followed the instructions contained in the demo readme, i.e.: feature:repo-add cxf 3.1.6 feature:install cxf-jaxrs cxf-transports-websocket-server install -s mvn:org.apache.cxf.samples/jax_rs_websocket_osgi/3.1.6 It's when

IndexOutOfBoundsException when "Authorization" header is empty String

Dear all, I am testing on a REST api, running on CXF 3.1.6 over pax-web 4.2.6. The API accepts a header "Authorization". The problem is that if the value is provided for the header, everything is fine and the behaviour is expected (HTTP status 401 or 200, depending if the value is correct or