[jira] [Commented] (BEAM-585) Support other message than TextMessage in JmsIO

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-585:
------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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é
>            Priority: P2
>              Labels: stale-P2
>
> 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)