I do think we should have a more clear picture how Camel kick-starts itself. Currently you can do it in several ways according to your needs and Camel is pretty smart in that regard.
You can start Camel with:
- Standalone with your own java main code
- Using camel-spring Main class
- From maven tools
- Spring configured (a normal use-case)
- Web-app with spring configured
- OSGi activator (or how does it do this?)
And on a related note as well, how to easy do unit testing of your own camel integrations
- standard junit
- using camel-core-tests
- using camel-spring-tests
- using spring unit tests with all its annotations etc
- etc.
Task
Open
Major
Document - how does Camel kickstart itself 