You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Tony Kurc (JIRA)" <ji...@apache.org> on 2015/11/07 04:16:10 UTC

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

     [ https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tony Kurc updated NIFI-614:
---------------------------
    Fix Version/s:     (was: 0.4.0)
                   1.0.0

> 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: 1.0.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)