Thanks for the reply & sorry for the autocorrect error in the subject. Meant to be Messenging.
The two options are: A separate process or a module/library that extends QPid. For the former I can get info from the docs, but haven't seen anything to help me with the latter. /~Nicolas On 13 May 2011 9:23 PM, "Steve Huston" <shus...@riverace.com> wrote: > Hi Nicolas, > >> Firstly, my apologies if this question has been asked and >> answered multiple times. > > No problem. And welcome. > >> I am evaluating a number of EMSs, ESBs and SOA stacks, both >> non-free and F/OSS. >> >> We are using a proprietary, in-house developed messaging >> layer developed 10 years ago, with a few bug fixes since then >> (yeh, don't say a thing about that, I've only been there 6 >> months). Our system vaguely resembles SOA. > > Ok. > >> I want to attach one of our clients and services to QPid, >> without having to recompile them (the coupling and cohesion >> is way too tight for a basic evaluation) >> >> I want to create a message handler/adapter to attach to QPid >> that talks our protocols, doing the necessary translation. Is >> this possible? How? The only other option is to create a >> separate gateway that does the translation, linking QPid with >> our broker. > > I'm not sure what the difference between those two options are, but, > yes, you can write an adapter that interfaces to qpid on one side and > feeds/digests things from your existing broker. SMOP :-) > > -Steve > > -- > Steve Huston, Riverace Corporation > Total Lifecycle Support for Your Networked Applications > http://www.riverace.com > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:users-subscr...@qpid.apache.org >
