I am going to risk answering your question....
Camel is an implementation of Enterprise Integration Patterns in Java.
If you use a message-oriented architecture for your application(s) or systems in your company, it is a great API to easily use any kind of transport / filtering / interception mechanism and carry messages from one point to another with many possibilities. Camel supports Spring, which allows for very few code in an application and a LOT of possibilities in handling messages. And the cherry on top of the Camel cake is that "message" can be any object you want. So you can carry and massage any data coming in and spit it in various forms and ways to various destinations.
An example I can give is taken from RL experience: implementing a SMS router/proxy using Camel: a SMS comes in; a SMS count is sent (by Camel) to a customer DB to bill him later, while this SMS goes through a (Camel) filter that finds out which carrier it should go to. The SMS is then forwarded (by Camel) to its actual transport destination....etc.
The beauty of Camel is that, besides having a full-blown implementation of Enterprise Patterns, you can do other things than just handling messages. I actually wrote a Wikipedia Dictionnary parser with it...
Get a dictionnary entry from an URL ->Filter bad chars->XML-ise it -> Send into DB and record to log...
If your company is SOA oriented or your applications are workflow-based, Camel is a GREAT solution.