camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Protocol conversion / active mediation
Date Mon, 17 May 2010 06:31:34 GMT
On Sun, May 16, 2010 at 6:11 PM, vabia <lui-29@tlen.pl> wrote:
>
> Hi
>
> Thanks but this is part is more or less clear. What is not clear is how to
> use Camel in "server mode". And this should be treated literally, I’m
> looking for some library / framework / concept that will handle starting new
> threads upon new requests, re-queuing incoming / outcoming requests,
> re-tries etc.
>

You can look at the components offered out of the box
http://camel.apache.org/components.html

For example if its HTTP based then Jetty can act as a server
Or TCP/UDP you ca go with Apache Mina or JBoss Netty.



> BR,
>
>
> Claus Ibsen-2 wrote:
>>
>> 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 <lui-29@tlen.pl> 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
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Protocol-conversion---active-mediation-tp28573662p28575659.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

Mime
View raw message