[
https://issues.apache.org/jira/browse/NIFI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193503#comment-15193503
]
Joseph Witt commented on NIFI-614:
----------------------------------
#1) I agree is a problem and should be overcome.
For #2 and #3 I think this is the crux of the change. We have tried to support
JMS with a nicer user experience like the one you're advocating for. But this
simply breaks down with vendor specific implementations and worse their
versions. So, by instead going to a lower quality user experience augmented by
improved documentation for this particular protocol (JMS) we can support any
JMS vendor provided they use standard bean conventions for setting these.
I don't love this either Mike. But i do love it much more than what we had.
We should fix #1 but for #2 and #3 I think this is the right tradeoff - imho.
Thanks
Joe
> 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)
