Random ramblings on Open Source, integration and other malarkey
Hi James,I put also an entry on my bloghttp://www.davidgreco.it/MySite/Blog/Entries/2008/2/4_I’m_a_Camel_rider_%21.html
Great to see a concrete example! I joined the MOM boat a bit late and chanced upon your blog while investigating activeMQ + camel.I was able to run the example but I think that I haven't fully grokked Camel + activeMQ + esper conceptually & how to apply this new paradigm to architectural designs. It would be interesting if you shared a bit more about architectural designs for using Camel + active MQ + Esper. From what I understood, if I'm using an async request/response message architecture, the code performing the receive/process/send linkage could be 'thrown away' by delegating message processing to Esper and routing to camel... E.g. in an ActiveMQ application using MDPs (jencks), the 'normal' way of doing it would be to use onMessage() to process requests, generate responses and route/send them. Using camel + esper, I could use camel + esper as follows: from([clientRequestQueue]).process([prepareSvrResponseUsingEsper]).to([clientResponseQueue]). Am I on the right track? I will be playing more with the JMS examples that come with esper to learn more...
Yes, you're on the right track :)You can use Camel to route events or messages from any protocol to some processor, bean or transformation then reply or send the response somewhere else.A common use case is using the Bean Integration to bind Java methods on beans to message flows...http://activemq.apache.org/camel/bean-integration.html
Hi, I could not find the exampleplease forward the example at my email idThanks
Post a Comment