D
dbeavon
Guest
I was having a bit of trouble with the "JMS generic adapter" today. It set me to wondering if anyone has any experience with the "in-process" hosting of a messaging client within an ABL process (eg. _mproapsv). Perhaps this could be done with the help of the "CLR bridge"? For example, if I have the AMQ client libraries for .Net from nuget, then I should be able to load them directly into an ms-agent process and start sending messages straight to an AMQ broker. This would be a nice improvement over "broker-connect" whereby you need the "broker-adapter-thingy". That thing runs as a separate process and, based on my understanding, it accomplishes little more than provide an independent hosting process for the JMS client libraries. It also introduces complexity during configuration and deployment. It also adds an additional point of failure. I've never been a huge fan of that thing. Please let me know if anyone has ever used an "in-process" messaging client from ABL that communicates directly to a messaging broker. It doesn't seem too far out of reach. I'd rather not re-invent this from scratch if someone has already done it. We are using RedHat AMQ for our broker.
Continue reading...
Continue reading...