: It's a shame to see that we seem to maybe need to use the underlying Apache : HttpClient in tests thanks to the presence of SSL randomization. Hossman, : do you have ideas on how we could not have such a dependency?
Hmmm... that feels like a miss caracterization of the situation? SSL randomization doesn't mean tests (that need a direct HTTP connection) "need" to use Apache HttpClient -- it just means tests (that need a direct HTTP connection) need to use *SOME* sort of HTTP client configured with the correct trust store, key store, clientAuth settings, etc... The test framework -- and more to the point: HttpSolrClient -- make it trivial to get an Apache HttpClient that is already correctly configured acording to the test randomization. So that's what devs use when writting tests. If there was another way for devs to get some other other HTTP client impl that was correctly configured, and just as easy to use as an Apache HttpClient, then we could probably refactor Apache HttpClient out of all the tests. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
