[
https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189777#comment-15189777
]
ASF GitHub Bot commented on NIFI-614:
-------------------------------------
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/222#issuecomment-195006367
Following the pattern for Controller Services and their API in
nifi-standard-services, JMSConnectionFactoryProviderDefinition should be in
it's own package.
> 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)
