Yes that exactly the sort of thing I had in mind. The exact phase isn't really that important in this case, as the real action occurs asynchronously, presumably a relatively long time after *all* the outbound phases have been traversed. (Assuming the timeout is realistically long)
Cheers, Eoghan On 9 March 2010 16:58, Andrew Clegg <[email protected]> wrote: > > > Eoghan Glynn-4 wrote: > > > > 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. > > > > Is this the kind of thing you mean? > > http://pastebin.com/yxkwULAK > > It seems to work so far but I need to test it a bit more thoroughly to make > sure it's not doing anything completely unexpected. I'd appreciate any > feedback about whether it's attached to the right phase (PRE_STREAM) too, > as > I'm not too familiar with interceptors. > > Thanks, > > Andrew. > > -- > View this message in context: > http://old.nabble.com/How-to-get-HttpURLConnection-of-Dispatch-client-tp27834705p27838542.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
