Just another thing:
- Camel is a mediation, routing and EIP framework
- ServiceMix is complete ESB platform, where Camel is the prefered
routing framework
to summarize in few words :)
Regards
JB
On 02/28/2011 10:38 AM, janne postilista wrote:
The roles of ServiceMix 4 and Camel (and others) are a bit confusing to me.
Take the ServiceMix architecture pictured as:
http://fusesource.com/docs/esb/4.3.1/esb_getting_started/ESBGetStartedArchIntro.html
(could not find similar pic in servicemix.apache.org)
Lets say I'm building an integration system which reads from an JMS
queue A, does some processing to the messages, and writes them to
another queue B.
Wouldn't I just implement all of this inside Camel? Camel has features
for routing and processing the messages, and components for reading /
writing all kinds of protocols (JMS/file/ftp/...). Is this a typical
way of using ServiceMix?
In which situations it would be better to use the parts outside of
Camel, pictured in
http://fusesource.com/docs/esb/4.3.1/esb_getting_started/ESBGetStartedArchIntro.html
- NMR, JMS, JAX-WS?
