camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-782) Tracer incorrectly treats messages with InputStream as body
Date Wed, 06 Aug 2008 04:17:52 GMT

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

Claus Ibsen updated CAMEL-782:
------------------------------

        Fix Version/s: 1.5.0
    Affects Version/s: 1.4.0

> 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
>             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.


Mime
View raw message