[
https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297534#comment-16297534
]
ASF GitHub Bot commented on NIFI-614:
-------------------------------------
Github user mosermw commented on the issue:
https://github.com/apache/nifi/pull/222
Since TIBCO libraries don't fall under a license that is compatible with
the Apache License 2.0, Apache NiFi cannot distribute a solution that is
specific to TIBCO. But you should be able to build an extension to Apache NiFi
that works for you. Here is an example for how you might approach building a
NiFi extension for this
[mosermw/nifi-jms-providers-bundle](https://github.com/mosermw/nifi-jms-providers-bundle).
> 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)
