[
https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961205#comment-14961205
]
Mark Payne commented on NIFI-614:
---------------------------------
I accidentally created a duplicate of this ticket (NIFI-1040). The description
that I had was as follows, since it provides a few additional thoughts here:
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.
> 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
> Labels: JMS
> Fix For: 0.4.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)
