You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2016/01/13 02:32:39 UTC
[jira] [Commented] (CAMEL-9506) STOMP component does not handle
stream objects
[ https://issues.apache.org/jira/browse/CAMEL-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095403#comment-15095403 ]
Willem Jiang commented on CAMEL-9506:
-------------------------------------
I just checked the code of camel stomp endpoint, it should not use the toString() directly on the message body.
The fix is on the way :)
> 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
> Assignee: Willem Jiang
>
> 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)