[SWS-835] HttpComponentsMessageSender inintuitive constructor Created: 22/Jun/13  Updated: 19/Aug/13  Resolved: 03/Jul/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: Erik van Konijnenburg Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relates to SWS-838 HttpComponentsMessageSender: Use the ... Resolved


HttpComponentsMessageSender has two constructors, with and without HttpClient, and the one with HttpClient omits adding a SoapRemoveHeaderInterceptor.

This breaks in org.apache.http.protocol.RequestContent with
new ProtocolException("Content-Length header already present"),
but only in some containers (oc4j) and not in others (jetty, eclipe); this makes the issue hard to debug.

Adding a note to the javadoc would help the developer pick the proper constructor to avoid this issue.

git pull request coming up.

Comment by Arjen Poutsma [ 02/Jul/13 ]

Git pull request at https://github.com/SpringSource/spring-ws/pull/5

Generated at Mon Nov 19 17:37:42 UTC 2018 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.