[ https://issues.apache.org/jira/browse/HTTPASYNC-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503793#comment-17503793 ]
Oleg Kalnichevski commented on HTTPASYNC-168: --------------------------------------------- > why WONT-FIX ? [~fernandosci] Because it is fairer than fixing the issue in subversion and never releasing 4.1.6. > Even though this is an undocumented and unsupported feature it is being used > by Apache CXF and the fact is that right now This is the risk of using undocument / unsupported features Oleg > 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