[jira] [Commented] (NIFI-614) Create a JMS ConnectionFactory controller service and refactor JMS processors to use it

["Joseph Witt (JIRA)" <ji...@apache.org>]

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

Joseph Witt commented on NIFI-614:
----------------------------------

moved to 060.  Recommend we do support this model with specific connection factories that understand the intricacies of various providers such as ActiveMQ, IBM MQ, Tibco and allows the user to specify the necessary Jar in the event of non ASLv2 compatible items.  We can then provide new JMS processors such as ProduceJMS and ConsumeJMS or adapt the existing ones to leverage these controller services optionally.

> Create a JMS ConnectionFactory controller service and refactor JMS processors to use it
> ---------------------------------------------------------------------------------------
>
>                 Key: NIFI-614
>                 URL: https://issues.apache.org/jira/browse/NIFI-614
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 0.1.0
>            Reporter: Michael Moser
>            Assignee: Oleg Zhurakousky
>              Labels: JMS
>             Fix For: 0.6.0
>
>
> It is difficult to extend the standard JMS processors to use a different JMS provider besides the included ActiveMQ.  Improve the process of adding support for other JMS providers.
> Create a JMS ConnectionFactoryService API in nifi-standard-services.  Create an ActiveMQConnectionFactoryService with the ActiveMQ implementation in nifi-standard-services.  Modify the JMS processors in nifi-standard-processors to use a ConnectionFactoryService to pick the JMS Provider to use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)