[ 
https://issues.apache.org/jira/browse/CAMEL-14823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vojtech Fried updated CAMEL-14823:
----------------------------------
    Description: Current camel-servlet doesn't support to disable the stream 
caching from the camel context, it just check the exchange property for it. The 
cloned CAMEL-8821 Jira tried to fix it, but the fix does not work. As the last 
comment there says, readRequestBodyFromServletRequest calls a wrong method 
("readResponse..." instead of "readRequest...", only the latter contains the 
fix). Either those two methods could be merged into one (with the body of 
"readRequest...") or readRequestBodyFromServletRequest  should call 
"readRequest...".  (was: Current camel-servlet doesn't support to disable the 
stream caching from the camel context, it just check the exchange property for 
it. The cloned Jira tried to fix it, but the fix does not work.)

> Support to disable the stream caching in camel-servlet from the camel context 
> - once more
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-14823
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14823
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-servlet
>    Affects Versions: 2.25.0, 3.1.0
>            Reporter: Vojtech Fried
>            Assignee: Willem Jiang
>            Priority: Major
>
> Current camel-servlet doesn't support to disable the stream caching from the 
> camel context, it just check the exchange property for it. The cloned 
> CAMEL-8821 Jira tried to fix it, but the fix does not work. As the last 
> comment there says, readRequestBodyFromServletRequest calls a wrong method 
> ("readResponse..." instead of "readRequest...", only the latter contains the 
> fix). Either those two methods could be merged into one (with the body of 
> "readRequest...") or readRequestBodyFromServletRequest  should call 
> "readRequest...".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to