Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 12 Jan 2016 20:35:40 +0000 (UTC)
From: "Alex Ford (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12929587.1452630926000.89968.1452630940381@Atlassian.JIRA>
In-Reply-To: <JIRA.12929587.1452630926000@Atlassian.JIRA>
References: <JIRA.12929587.1452630926000@Atlassian.JIRA>
 <JIRA.12929587.1452630926150@arcas>
Subject: [jira] [Created] (CAMEL-9506) STOMP component does not handle
 stream objects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Alex Ford created CAMEL-9506:
--------------------------------

             Summary: STOMP component does not handle stream objects
                 Key: CAMEL-9506
                 URL: https://issues.apache.org/jira/browse/CAMEL-9506
             Project: Camel
          Issue Type: Bug
          Components: camel-stomp
    Affects Versions: 2.16.1
            Reporter: Alex Ford


The STOMP component only performs a very simple toString() on the body of the incoming exchange when it creates a STOMP message. This does not work when the body does not support a toString() which gives some reasonable human readable representation of the object. This is exactly the case if you try to do the following:

{code}
from("direct:a").marshal().json(JsonLibrary.Gson).to("stomp:topic:foobar")
{code}

The result of the JSON serialization is a Stream, and the toString() on a Stream results in an object hash (e.g. "[B@30479402"). A more appropriate thing to do here is similar to what the File component does. (Basically, read the stream for the data.)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)