[
https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193499#comment-15193499
]
Oleg Zhurakousky commented on NIFI-614:
---------------------------------------
[~mosermw] Below should address all 3 points, but before, keep in mind that
this was NOT designed with any specific broker in mind. It was designed for all
known JMS brokers and currently been tested with ActiveMQ, IBM MQ (several
versions) and Tibco.
1. Yes, single CS per URI of the broker, but multiple processor instances can
talk to multiple destinations in that broker, so only if your flow talks to
multiple broker you would need multiple CS.
2. Yes, due to the fact that we can NOT distribute non-OS client libraries
(i.e., IBM, Tibco) the admin who will configure ConnectionFactory CS must know
what libraries are required and where they are are
3. I think #2 answers it. Also, keep in mind that this new JMS support also
allows multiple versions of the same client library. So component itself
becomes very thin since it only depends on JMS while specific implementation
provided by the DFM
> 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)
