[
https://issues.apache.org/jira/browse/CAMEL-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028054#comment-16028054
]
Stephan Siano commented on CAMEL-8419:
--------------------------------------
The issue still occurs with newer versions, so yes, we should consider this. I
still don't have a better idea than copying the Camel stream cache into a CXF
stream cache, but maybe some CXF expert has a good idea for this.
> Camel StreamCache does not work with CXF consumer for InOut messages
> --------------------------------------------------------------------
>
> Key: CAMEL-8419
> URL: https://issues.apache.org/jira/browse/CAMEL-8419
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.14.1
> Reporter: Stephan Siano
> Attachments:
> 0001-CAMEL-8419-Camel-StreamCache-does-not-work-with-CXF-.patch
>
>
> If a route that is started by a CXF consumer and has an InOut exchange
> pattern (meaning that the CXF consumer is returning a response back to the
> caller) contains a StreamCache as message object that is not in memory,
> returning the payload will fail.
> The reason for this is that an on-disk stream cache in Camel will be removed
> when the LUW ends, but CXF will return the response afterwards.
> See the two attached unit tests for details.
> I don't like the actual patch too much, as it copies on-disk camel stream
> caches into CXF stream caches when creating the CXF message object in camel
> CXF, but this is about the last step before the LUW ends (and the file gets
> deleted).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
