camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-10721) Camel Connectors
Date Wed, 01 Mar 2017 09:23:45 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-10721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-10721.
---------------------------------
    Resolution: Fixed

> Camel Connectors
> ----------------
>
>                 Key: CAMEL-10721
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10721
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.19.0
>
>
> Introduce Camel Connectors.
> A Camel Connectors is a simplified and pre-configured Camel component which has been
setup for a specific use-case, such as "add new contact to salesforce", or "add calender entry"
or whatever.
> This would allow to build a marketplace/catalog of Camel connectors which would be easier
to use for business use-cases. 
> The connector is based on one of the existing Camel components (or 3rd party component)
by which you can specify in a camel-connector.json file which options to pre-select and as
well specify other default values etc. 
> Then a maven plugin will build this as a Camel component, so at runtime its just a regular
Camel component. 
> And because they are just regular Camel component then there is no problem running them
in Camel applications. 
> In addition all existing JMX, tooling et all just sees this as Camel components and can
use that.
> Also at design time, for example the IDEA plugin will see the connector as a 3rd party
Camel component and offer code assistance to it etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message