Hi Short answer yes Camel is a perfect fit for that.
I suggest to read this great article introducing Camel http://architects.dzone.com/articles/apache-camel-integration You can easily plugin your own Component which supports the protocol(s) you need to use. And have it work seamless with Camel. On Sun, May 16, 2010 at 11:58 AM, vabia <[email protected]> wrote: > > Hello, > > I was looking for a library / framework for protocol conversion / active > mediation. The scenario it should support is at follow: > - some message in protocol A comes to the box from machine A > - we parse the message, get what's important and send it to machine B > via protocol B > - get response from machine B, parse and send it to machine A > - > The main requirements are: > - easily pluginable with new protocols > - "light" (clustering, paging etc. are not required) > - easy to deploy > - mature > > > I found that Apache Camel can be an option (based on this info: > http://stackoverflow.com/questions/229423/protocol-conversion-normalization-biztalk-alternatives/229793#229793). > But now I'm wondering how to make it a fast and reliable solution (without > reinventing the wheel) by adding queuing, re-tries etc. Based on what I read > Apache ServiceMix can be an option but in my scenario there’s rather need > for mediator (A to B, C to D etc) and not for "bus". Is there any working > example for the abovementioned scenario? > > BR, > > -- > View this message in context: > http://old.nabble.com/Protocol-conversion---active-mediation-tp28573662p28573662.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
