You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Michael Moser (JIRA)" <ji...@apache.org> on 2015/12/02 16:23:10 UTC
[jira] [Updated] (NIFI-1040) Refactor JMS Processors to use
Controller Services for JMS Providers
[ https://issues.apache.org/jira/browse/NIFI-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Moser updated NIFI-1040:
--------------------------------
Fix Version/s: (was: 0.4.0)
0.5.0
> Refactor JMS Processors to use Controller Services for JMS Providers
> --------------------------------------------------------------------
>
> Key: NIFI-1040
> URL: https://issues.apache.org/jira/browse/NIFI-1040
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Fix For: 0.5.0
>
>
> Currently, the JMS Processors only support ActiveMQ. Adding many additional JMS Providers is difficult because of licensing incompatibilities. By refactoring these processors to use a Controller Service for configuring the JMS Provider, we can allow others to much more easily create their own Controller Services that will work with the JMS processors.
> This ticket should encompass building an ActiveMQJMSProvider controller service in addition to updating the Processors to make use of this.
> The versioning scheme that we use for Apache NiFi does allow this in minor release, since it will not change the behavior of the flows, other than to make the Processors invalid. However, since this will make existing JMS Processors invalid, it is important that the Release Notes highlight this so that there are no surprises.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)