With Connectors there is a ability to provide simplified one use case focused Camel components, I think this can be further extended to have a way of creating Components/Connectors out of Routes (perhaps just from RouteDefinition).
A component that would look like any other Camel component but would be defined using a route.
This would enable more functionality in a simple to use component.
One example of this would be getting data out of Salesforce on change within Salesforce. Currently you would need to string two Salesforce endpoints: a streaming consumer and a fetching producer, something like:
could be simplified into:
Currently Connectors have pre/post processors that can achieve something similar, but this would enable more complex use cases.