[SWS-838] HttpComponentsMessageSender: Use the PoolingClientConnectionManager instead of the deprecated ThreadSafeClientConnManager Created: 10/Jul/13  Updated: 19/Aug/13  Resolved: 19/Aug/13

Status: Resolved
Project: Spring Web Services
Component/s: Core
Affects Version/s: 2.1.3
Fix Version/s: 2.1.4

Type: Improvement Priority: Minor
Reporter: Martin Wegner Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
is related to SWS-835 HttpComponentsMessageSender inintuiti... Resolved

 Description   

HttpComponentsMessageSender (no argument constructor):

The ThreadSafeClientConnManager is deprecated since Apache HttpClient 4.2.
The recommendation is to use the PoolingClientConnectionManager instead.

########################################

If I use the HttpComponentsMessageSender constructor with the HttpClient argument, then I can't add the RemoveSoapHeadersInterceptor to the HttpClient object (which extends the AbstractHttpClient) because this HttpRequestInterceptor is a private inner class.

Therefore I can't see a workaround to use the PoolingClientConnectionManager.



 Comments   
Comment by Arjen Poutsma [ 19/Aug/13 ]

Fixed. The RemoveSoapHeadersInterceptor is now a public class, so you can use it in the non-default constructor as well (see SWS-835).

Generated at Sat Nov 17 12:55:03 UTC 2018 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.