[
https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301389#comment-16301389
]
ASF GitHub Bot commented on NIFI-614:
-------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/222
@jugi92 you're right that the NIFi support for dynamic/custom attributes to
help with Vendor differences. However, even in that case it appears (though
I've not personally verified) that this isn't enough in the Tibco case for
getting TLS setup propertly for them. For the NiFi method to work the custom
attributes need to correspond to bean properties/setters. If their approach
requires more awareness then it will require a specific component for them. I
am aware of plenty of NiFi/Tibco integrations but they're outside of Apache at
this point given what Mike highlighted above.
If you are able to investigate the Tibco TLS setup requirements and see
what the gap is perhaps it can be done in a vendor neutral way
> 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)
