I think CXF WebClient already take care of it, the response is input stream, the user should close it himself.
In camel-http, the http client auto close the connection when it out of scope, so we have to copy the stream in camel for the outside usage. But it’s the user responsibility to close the stream after consuming the stream. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On November 27, 2014 at 10:00:16 PM, thib (thibaut.rob...@gmail.com) wrote: > Thanks, I looked at your fix, seems prefectly fine for my usage. I have one > question however: > Should'nt you close the connection also when responseClass is provided ? > (whatever the exchange pattern) > > I would think that response/connection should be left open only when we are > able to consume (and close) it from the outside, meaning: responseClass is > null or Response, and exchange is out capable. > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/CxfRs-producer-connection-not-closed-tp5759664p5759711.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
