Apache Camel has not been ported to any other language. In a sense, there is no reason to port it. The whole point of Camel is Enterprise integration. All it really does is route and process messages.
If you need it to interact with a Sharepoint or .NET application, you can define a Camel Endpoint for whatever messaging or transport system you are using.
What problem are you trying to solve? I dont really know what you mean by:
allows web service messages to be determined dynamically during run
time
The messages arent determined dynamically... whatever that means. Camel provides an implementation of many Enterprise Integration Patterns (EIP), but it needs to know the type of whatever message it is routing.
Camel has hundreds of automatic conversions, so it may seem like magic, but the truth is that jsut like anything else in Java, everything within Camel is type safe.