You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2008/08/26 10:31:54 UTC

[jira] Assigned: (CAMEL-782) Tracer incorrectly treats messages with InputStream as body

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

Willem Jiang reassigned CAMEL-782:
----------------------------------

    Assignee: Willem Jiang

> Tracer incorrectly treats messages with InputStream as body
> -----------------------------------------------------------
>
>                 Key: CAMEL-782
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-782
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Genadii Ganebnyi
>            Assignee: Willem Jiang
>             Fix For: 1.5.0
>
>
> Suppose we have the following flow:
>  from("activemq:vasea")
>   .to("cxf:bean:serviceEndpoint?dataFormat=MESSAGE")
>     .unmarshal().string()
>   .to("activemq:petea");
> In this flow cxf:bean:serviceEndpoint returns ByteArrayInputStream as body. Under normal conditions everything works fine: WS output gets to the queue.
> But if we add:
> getContext().addInterceptStrategy(new Tracer());
> Queue starts receiving empty messages. After digging in the code I found out that tracer reads input stream in order to display body, but not resets it. Thus when message reaches unmarshaller, nothing could be read from the stream.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.