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
