[ 
https://issues.apache.org/jira/browse/HTTPASYNC-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503789#comment-17503789
 ] 

Francisco Bento da Silva Neto commented on HTTPASYNC-168:
---------------------------------------------------------

Hi [~olegk] , why WONT-FIX ?

The scope of the change 
[https://github.com/apache/httpasyncclient/commit/94b061bae5fe247cf3e69b487a78b457f20ca2e2]was
 clearly to use camelCase on java internal members, but it did accidentally 
touched a configuration (probably due to a find->replace mistake) that changed 
a configuration param value. If the intention was to really change the config 
param name, I'd expect at least a minor version increment (not patch).

Just to give a background: I stumbled upon this issue while upgrading a 
spring-boot application to the latest spring boot (2.6.3) and some 
nearest-dependency brought 4.1.5 with CXF (we use CXF for soap client), and 
this patch broke our application.

Even though this is an undocumented and unsupported feature it is being used by 
Apache CXF and the fact is that right now, CXF with async cannot be used on 
spring boot projects - or any project that brings 4.1.5.

See: 
[https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-dependencies/2.6.2/spring-boot-dependencies-2.6.2.pom]
 

{{<httpasyncclient.version>4.1.5</httpasyncclient.version>}}

 

> Renamed property key breaks Apache CXF
> --------------------------------------
>
>                 Key: HTTPASYNC-168
>                 URL: https://issues.apache.org/jira/browse/HTTPASYNC-168
>             Project: HttpComponents HttpAsyncClient
>          Issue Type: Bug
>    Affects Versions: 4.1.5
>            Reporter: Fernando Soares Carnevale Ito
>            Priority: Major
>
> The value of property 
> IOSESSION_FACTORY_REGISTRY defined in the class 
> PoolingNHttpClientConnectionManager was rename from 
> "http.iosession-factory-registry" to 
> "http.ioSession-factory-registry"
>  
> I realize that this property is not public but, for example, APACHE CXF uses 
> it and other projects might be using it too.
>  
> I believe that this property was renamed by accident and this issue is to 
> check whether it is possible to revert this rename



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to