You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/26 20:31:00 UTC
[jira] [Commented] (NIFI-614) Create a JMS ConnectionFactory
controller service and refactor JMS processors to use it
[ https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454820#comment-16454820 ]
ASF GitHub Bot commented on NIFI-614:
-------------------------------------
Github user ragnarotech commented on the issue:
https://github.com/apache/nifi/pull/222
@jugi92 this solution does not work with tibjms.jar v8.x In v8 tibco adds "void setSSLTrustedCertificate(byte[] certificate, java.lang.String trustedEncoding)" to it's TibjmsConnectionFactory class, which is what method the jms util finds first causing a too few arguments exception.
> 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
> Priority: Major
> 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
(v7.6.3#76005)