cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: [1/2] cxf git commit: [CXF-7060] Provide a cxf-http-provider feature to be used when in need of a provider-agnostic http transport
Date Tue, 20 Sep 2016 13:25:30 GMT

> On Sep 20, 2016, at 9:07 AM, gnodet@apache.org 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
dkulp@apache.org <mailto:dkulp@apache.org> - http://dankulp.com/blog <http://dankulp.com/blog>
Talend Community Coder - http://coders.talend.com <http://coders.talend.com/>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message