[
https://issues.apache.org/jira/browse/CAMEL-10798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977734#comment-15977734
]
ASF GitHub Bot commented on CAMEL-10798:
----------------------------------------
GitHub user igarashitm opened a pull request:
https://github.com/apache/camel/pull/1648
CAMEL-10798 Splitted camel-ignite component for each endpoint
I've been looking for a easy way to get around CAMEL-11150, but it turned
out it's easier to address CAMEL-10798. This splits the ignite component into 7
which corresponds to each ignite endpoint, and also it preserves existing
IgniteComponent with deprecated flag. In this way the old syntax like
`ignite:cache` is still allowed with having WARN log saying that the syntax has
been deprecated.
I wonder it may be a bit too big change at this stage as 2.19.0 release is
around the corner though. If so let's just have it after the release.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/igarashitm/camel CAMEL-10798-ignite
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1648.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1648
----
commit c5b52455871b6e17d06fd21dcee0a0957f32525c
Author: Tomohisa Igarashi <tm.igara...@gmail.com>
Date: 2017-04-19T14:21:30Z
CAMEL-10798 Splitted camel-ignite component for each endpoint
----
> 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: 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)
