Wrong path my friend.
Camel is not a "service container". It is a message routing framework. It
routes messages (in which might contain a data object, a file, an xml,
etc...)
You can "send" and/or "receive" messages with Camel, using different
protocols, some remote, some not. It is up to you on how to start/end the
route.
You can though achieve what you want with Camel, but if you will be writing
routes with only two endpoints, it will be useless.
Now, if you want one entry point only, and from there find out which
service should be invoked based on some data, then Camel is the right way
to go.
If you want to know more about it, let us know.
Cheers,
Bruno
