[
https://issues.apache.org/jira/browse/CAMEL-11475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-11475.
---------------------------------
Resolution: Won't Fix
connectors has been removed
> Provide a route Connector/Component
> -----------------------------------
>
> Key: CAMEL-11475
> URL: https://issues.apache.org/jira/browse/CAMEL-11475
> Project: Camel
> Issue Type: New Feature
> Components: camel-connector, camel-core
> Reporter: Zoran Regvart
> Priority: Major
>
> 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:
> {code:java}
> from("salesforce:accountsTopic?...")
> .setHeader("sObjectId", ...)
> .to("salesforce:getSObject?...")
> {code}
> could be simplified into:
> {code:java}
> from("salesforce-account-updates")
> {code}
> Currently Connectors have pre/post processors that can achieve something
> similar, but this would enable more complex use cases.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
