camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Siano (JIRA)" <>
Subject [jira] [Updated] (CAMEL-8419) Camel StreamCache does not work with CXF consumer for InOut messages
Date Mon, 04 May 2015 11:35:06 GMT


Stephan Siano updated CAMEL-8419:
    Attachment: 0001-CAMEL-8419-Camel-StreamCache-does-not-work-with-CXF-.patch

The initial patch was not closing the CachedOutputStream.

I agree with Claus, that it would be better to have a callback that was ending the Camel LUW
once CXF has finished processing the message (not when giving the control back to CXF), but
I have not yet found any facility in CXF for that.

> Camel StreamCache does not work with CXF consumer for InOut messages
> --------------------------------------------------------------------
>                 Key: CAMEL-8419
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.14.1
>            Reporter: Stephan Siano
>             Fix For: 2.15.2, 2.16.0
>         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

View raw message