I work with some middleware that makes SOAP calls with an ad hoc internal framework using HttpClient 3.0.1. We set the "socket timeout" on HttpClient, but we were really intending that to be an absolute timeout on the web service call. The socket timeout is really only used "per packet" so it's very easy for absolute times on service calls to be well over the "read timeout" value.
As I don't think I can fix this with HttpClient out of the box, I'm investigating the possibility of having a background task kill connections if they've gone past their time limit. What I'd like to ask here, though, is whether CXF has any direct or indirect support for solving this problem. I've been considering putting CXF in here instead of the ad hoc framework combined with raw HttpClient, but I'm looking for specific points to support this. If I could more easily support this "absolute time out" feature, that would be a plus.
