Good catch, I pick the wrong one. I think I need to move that capability to the web socket server transport instead which actually provides a HttpDestinationFactory.
2016-09-20 15:25 GMT+02:00 Daniel Kulp <[email protected]>: > > On Sep 20, 2016, at 9:07 AM, [email protected] wrote: > > <feature name="cxf-http-async" version="${project.version}"> > <feature version="${project.version}">cxf-http</feature> > @@ -166,6 +181,9 @@ > <bundle start-level="40">mvn:org.apache.httpcomponents/ > httpclient-osgi/${cxf.httpcomponents.client.version}</bundle> > <bundle start-level="40">mvn:org.apache.httpcomponents/ > httpasyncclient-osgi/${cxf.httpcomponents.asyncclient.version}</bundle> > <bundle start-level="40">mvn:org.apache.cxf/cxf-rt-transports- > http-hc/${project.version}</bundle> > + <capability> > + cxf.http.provider;name=async > + </capability> > </feature> > > > > The async is a client side only thing, not server side. The others seem > to be selecting the server side. Is this setting needed here? > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: [email protected] Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
