[ 
https://issues.apache.org/jira/browse/BEAM-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053398#comment-17053398
 ] 

Jean-Baptiste Onofré commented on BEAM-585:
-------------------------------------------

I'm moving forward on this Jira, supporting {{ByteMessage}}, {{MapMessage}}, ...

> Support other message than TextMessage in JmsIO
> -----------------------------------------------
>
>                 Key: BEAM-585
>                 URL: https://issues.apache.org/jira/browse/BEAM-585
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-jms
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>
> Now, the JmsIO only supports TextMessage coming from the broker. JMS broker 
> can provide other kind of messages like BytesMessage, MapMessage, 
> StreamMessage, ObjectMessage. The JmsIO should be able to deal with such kind 
> of messages (implicitly and explicitly). Depending of the JMS message type, 
> the JMS IO should use different coders.
> On the other hand, the JmsIO should allow users to deal with their own custom 
> coders.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to