I realize that Apache Camel doesn't have an abstraction similar to SI channels (which I like a lot), but apart from that:
Is it fair to say that the wiring of channels in a SI Spring Application context is similar to defining Camel routes? I would say so.
I want to represent "request execution recipes" that specify through which services (wrapped by Service Activators) a "request message" passes when it needs to assemble information from various sources. My thinking is to have different SI channel routes so that this would be specified in the AppContext.xml file.


Reply With Quote
