[ https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195416#comment-15195416 ]
ASF GitHub Bot commented on NIFI-614: ------------------------------------- Github user olegz commented on the pull request: https://github.com/apache/nifi/pull/222#issuecomment-196855425 So the problem with Tibco and SSL is that Tibco does things differently then other providers. In other words they don't use SSLContext and instead rely on setting individual properties inside their implementation of ConnectionFactory. The good thing is we can extract them from SSLContext, but need ti know exactly what we need. That said, propose to release this new JMS support with understanding that it does not yet support Tibco SSL and add it later as part of the enhancement. > 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)