Camel uses a runtime strategy to discover features while it starts up. This is used to register components, languages, type converters etc.
If you are using the uber .jar (the big camel.jar) with all the camel components in a single .jar filen, the this problem can typically occur.
To remedy this either add the missing .jars to the classpath, or stop using the big .jar and use the fine grained jars.
See also How do I use a big (uber) JAR?