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] [Created] (CAMEL-10798) camel-twitter, camel-ignite - Make the uri endpoints separated
Date Tue, 07 Feb 2017 12:09:41 GMT
Claus Ibsen created CAMEL-10798:
-----------------------------------

             Summary: 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


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)

Mime
View raw message