Hi, Camel is primarily a router surrounded by other capabilities (processors, interceptors etc). Camel mediates between 2 or more technology endpoints and applies rules, transforms, integration patterns along the way.
Asynchronous behavior primarily involves setting up listeners backed by an eventing framework. Camel offers this core capability and supports it over several protocols, transports. If your solution is an all JMS solution (i.e a single protocol centric asynchronous application) a MOM would do the job just fine. However you would need to write the plumbing code yourself and embed it in your application. If however your solution needs to do this over several protocols, transports and technology stacks in a simple manner using DSL or Spring DSL (with no need to worry about the plumbing code) then Camel is a good choice. Cheers, Ashwin... AnuragS wrote: > > Does it make sense to use Apache Camel for making asynchronous calls? Or > the old fashioned MoM is good enough. > ----- --- Ashwin Karpe, Principal Consultant, PS - Opensource Center of Competence Progress Software Corporation 14 Oak Park Drive Bedford, MA 01730 --- +1-972-304-9084 (Office) +1-972-971-1700 (Mobile) ---- Blog: http://opensourceknowledge.blogspot.com/ -- View this message in context: http://www.nabble.com/Using-Apache-Camel-Asynchronously-tp22111353s22882p22115100.html Sent from the Camel - Users mailing list archive at Nabble.com.
