[
https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301664#comment-16301664
]
ASF GitHub Bot commented on NIFI-614:
-------------------------------------
Github user jugi92 commented on the issue:
https://github.com/apache/nifi/pull/222
I found out that it works if the SSL Context Service is configured
correctly and the dynamic property is provided as shown below:
Property | Value
----------|-----------
SSL Context Service | SSLContextServiceForJMS
SSLTrustedCertificate | /path/to/TrustedCertificate.cer
So the dynamic attributes are a really valuable thing.
Thanks
> 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)
