[
https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301384#comment-16301384
]
ASF GitHub Bot commented on NIFI-614:
-------------------------------------
Github user jugi92 commented on the issue:
https://github.com/apache/nifi/pull/222
I understand that Apache Nifi can not deliver custom solutions for
individual proprietary JMS providers. But as I understood, the dynamic property
was build exactly for the purpose to set custom attributes of the Connection
Factory as mentioned in the Documentation:
[JMSConnectionFactoryProvider](https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-jms-cf-service-nar/1.4.0/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html)
So the question is if this is working for other parameters and the
implementation on Tibco Site does not allow the dynamic setting of attributes
or is it a problem in Nifi that it does not call the set Method of the
attribute correctly?
> 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.4.14#64029)
