Yes, Camel is a framework which is used to model the flow of messages.
Actually all it requires is JVM, because the next concept, CamelContext, which is kind of "container for camel routes, endpoints, transformers, etc." comes with different flavours - DefaultCamelContext (to be run outside of any web, OSGi or JavaEE container), SpringCamelContext (to be run inside Spring Framework), OsgiSpringCamelContext (to be run with Spring-DM, which isn't maintained anymore), BlueprintCamelContext (to be run in BlueprintContainer (like Aries-Bluepring) inside OSGi framwork (like Karaf)).
In JBoss Fuse you usually deploy blueprint-based camel context.
Thanks for the quick response.
In one of the camel project which i downloaded from Apache camel website - in camel-context.xml I see routes, cxf , active mq defined and used to send and receive msgs. If all these components can be built WITHOUT using FUSE and camel can be run standalone - in which scenario/use case would one use FUSE ?
In my project the requirement is that all web service calls from Client go through FUSE for making it asynchronous (my manger mentions FUSE every time).
If this can we achieved using camel alone - i am trying to understand where does FUSE fit in here - as per my understanding i wont need FUSE?