You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/09/02 17:08:41 UTC
[jira] [Commented] (BEAM-676) Use a provider to create JMS
ConnectionFactory and avoid Serialization issues
[ https://issues.apache.org/jira/browse/BEAM-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189548#comment-17189548 ]
Beam JIRA Bot commented on BEAM-676:
------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.
> Use a provider to create JMS ConnectionFactory and avoid Serialization issues
> -----------------------------------------------------------------------------
>
> Key: BEAM-676
> URL: https://issues.apache.org/jira/browse/BEAM-676
> Project: Beam
> Issue Type: Improvement
> Components: io-java-jms
> Reporter: Jean-Baptiste Onofré
> Priority: P3
>
> The {{JmsIO}} uses JMS {{ConnectionFactory}} as configuration. Unfortunately, {{ConnectionFactory}} interface doesn't extend {{Serializable}} (even if most of the implementations are {{Serializable}}).
> Instead (as I'm doing for the {{JdbcIO}}), I propose to create a {{ConnectionFactoryConfiguration}} POJO to create the {{ConnectionFactory}} in the {{@Setup}} of the reader and writer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)