Hi Willem,
thanks for your quick reply. The issue is that I cannot disable
streamCaching in 2.3-SNAPSHOT anymore. This is what was changed in
DefaultHttpBinding.parseBody:
Before:
// otherwise use input stream
return HttpConverter.toInputStream(request);
Now:
// otherwise use input stream and we need to cache it first
InputStream is = HttpConverter.toInputStream(request,
httpMessage.getExchange());
if (is == null) {
return is;
}
// convert the input stream to StreamCache
try {
CachedOutputStream cos = new
CachedOutputStream(httpMessage.getExchange());
IOHelper.copy(is, cos);
return cos.getStreamCache();
} finally {
is.close();
}
This means, the CachedOutputStream is always used. I have tried to disable
this on the camelContext. But obviously the above code does not check this
option in the camelContext. So it is not possible anymore.
willem.jiang wrote:
>
> These changes just to make sure the we can still read the post message
> body even the body is form message.
>
> You can still configure the CachedOutputStream by using the camelContext
> properties, I don't know what kind of issue that the changes introduced
> to you.
>
> Willem
>
> _Jens wrote:
>> Hi,
>>
>> it seems to me that the DefaultHTTPBinding again uses a
>> CachedOutputStream.
>> This means that the binding cannot be used anymore with longer streams
>> and
>> that the streamCache option on the CamelContext bean is ignored. Is this
>> going to be the way the caching is done in 2.3?
>>
>> Thanks,
>> Jens
>
>
>
--
View this message in context:
http://old.nabble.com/2.3-SNAPSHOT%3A-Stream-Caching-again-enabled-by-Bug-Fix-for-Camel-2686-and-CAMEL-2694-%28rev-941275%29--tp28582952p28583243.html
Sent from the Camel - Users mailing list archive at Nabble.com.
