I hate spell checker. The last sentence in previous response should read compliant instead of compliment.
Sent from my iPhone > On Feb 6, 2016, at 17:46, Oleg Zhurakousky <[email protected]> > wrote: > > David > > Thank you so much for reaching out. > The reason why I am using RabbitMQ client library is because I am familiar > with it, but as you aware AMQP is a protocol-based specification therefore it > doesn’t mater which client library is used as long as they are compliant with > the protocol version and current implementation is based on AMQP 0.9.1. > Also, you are mentioning QPID client libraries. Do you have an opinion which > one is better since as I mentioned I just went with the one I know?. As far > as QPID JMS, are you saying that you are using QPID JMS layer to make AMQP > look like JMS? If so in my experience layering JMS over AMQP while possible > brings a lot of limitations of JMS. In any event would be nice to hear your > thoughts on that. > As far as your processor implementation. Sorry I didn’t have a chance to look > at them at the time of writing this response (will look later on), but do you > look at them as QPID specific (i.e., QPID vs RabbitMQ)? And if so what is in > them that is specific to QPID? The reason why I am asking (and you can see it > from discussion on JIRA) is that with this effort we are aiming for > processors that are compliment with specific protocol regardless of the > broker implementation used, so it must be neutral. > > Thanks for reaching out once again. > Cheers > Oleg > >> On Feb 6, 2016, at 5:19 PM, DAVID SMITH <[email protected]> wrote: >> >> Hi Guys >> | | This email has been sent from a virus-free computer protected by >> Avast. >> www.avast.com | >> >> >> As you may remember I have developed some processors that publish/subscribe >> to AMQP brokers, but I was having problems writing Junit tests for these >> processors. I was interested to see that you have been working on NiFi Pull >> Request 865. I have looked at your code for these processors, we are both >> using different property descriptors to allow messages to be published and >> pulled. I also noticed that you are using RabbitMQ libraries to connect to >> the broker, whereas I connect to the AMQP broker using the QPID JMS >> libraries. I can still see a use for my processors and I would still be >> interested getting my processors uploaded to run alongside yours in a future >> release of NiFi.I have tidied up my code and pushed it back to github: >> https://github.com/helicopterman22/nifi_amqp_processors.git >> I would appreciate your feedback Dave >> >> >> >> On Wednesday, 3 February 2016, 2:05, asfgit <[email protected]> wrote: >> >> >> Github user asfgit closed the pull request at: >> >> https://github.com/apache/nifi/pull/200 >> >> >> --- >> If your project is set up for it, you can reply to this email and have your >> reply appear on GitHub as well. If your project does not have this feature >> enabled and wishes so, or if the feature is enabled but not working, please >> contact infrastructure at [email protected] or file a JIRA ticket >> with INFRA. >> --- >
