You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (JIRA)" <ji...@apache.org> on 2017/05/09 07:58:04 UTC

[jira] [Updated] (CAMEL-10798) camel-twitter, camel-ignite - Make the uri endpoints separated

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

Andrea Cosentino updated CAMEL-10798:
-------------------------------------
    Fix Version/s:     (was: Future)
                   2.20.0

> camel-twitter, camel-ignite - Make the uri endpoints separated
> --------------------------------------------------------------
>
>                 Key: CAMEL-10798
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10798
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Claus Ibsen
>            Assignee: Tomohisa Igarashi
>             Fix For: 2.20.0
>
>
> They currently have the same @UriEndpoint that represents all of their possible endpoint combinations. This usually works fine for Camel components. But some components such as twitter, ignite, hazelcast etc do have to many different endpoints that have very specific options per different endpoint.
> We should split up this in different components so they are separated.
> So we have
> twitter-status
> twitter-search
> twitter-direct
> Or something.
> This will also help tooling, documentation, et all so they are clearly separated and there are no confusion. For example twitter mention do not support the delay option which only twitter search uses etc.



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