Eoghan Glynn-4 wrote:
> 
> The HTTPURLConnection is retrieved on demand when the invocation is being
> prepared. So its not statically associated with the interceptor chain.
> 
> However the HTTPConduit does cache the current connection in the
> HTTPConduit.KEY_HTTP_CONNECTION
> property (i.e. "http.connection") property on the message object, so you
> could experiment by writing an interceptor that retrieves the value of
> this
> property and manipulates the connection directly.
> 

Okay, thanks, I'll try that. It's a bit of a shame that there's no way to
force an ongoing request to abort. Would you be interested in a patch? Or is
this use case too unusual?

Cheers,

Andrew.

-- 
View this message in context: 
http://old.nabble.com/How-to-get-HttpURLConnection-of-Dispatch-client-tp27834705p27837275.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to