[
https://issues.apache.org/jira/browse/BEAM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved BEAM-675.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
> Introduce message mapper in JmsIO
> ---------------------------------
>
> Key: BEAM-675
> URL: https://issues.apache.org/jira/browse/BEAM-675
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-extensions
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 2.3.0
>
>
> Currently, the {{JmsIO}} deals with a {{JmsRecord}} and populates the reader
> populates the {{PCollection}} with it.
> It also deals "only" with {{TextMessage}}.
> It would be helpful to allow users to provide {{MessageMapper}} function
> allowing to "convert" the JMS Message as a custom POJO, and eventually deal
> with other type of JMS Message ({{BytesMessage}}, {{MapMessage}}, ...).
> By default, the IO will still use {{JmsRecord}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
