[ https://issues.apache.org/jira/browse/CAMEL-10798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855857#comment-15855857 ]
Claus Ibsen commented on CAMEL-10798: ------------------------------------- We may consider this for 2.19 to make this sooner, and we can have a way of supporting old uri syntaxes and make it log WARN so people have time to migrate. > 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 > Fix For: 2.19.0, 3.0.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)