[
https://issues.apache.org/jira/browse/IGNITE-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011543#comment-15011543
]
Raúl Kripalani commented on IGNITE-1790:
----------------------------------------
#1 Done.
#2 Agree but it's a bit late. The A#notNullOrEmpty method was introduced in 1.4
and has already been used in 4 other components. Moreover, the Kafka streamer
(which I based my first streamer on) also threw an IAE in this same case. I
don't think it's important. From the technical perspective it may be somewhat
inaccurate to use IAE, but from the functional perspective it more correct than
ISA.
#3 Yes, it makes sense to refactor StreamAdapter to add a start() method. We
can open a ticket for 1.6.
#4 It's not so important, as the element that actually important is the
consumer. This is the one that'll bind to ports, consume files, etc. And it's
last in the start chain. However, I have hardened the logic to stop all
services in case the init fails. That way we're more atomic.
Tests:
#1 Done. These annotations are JUnit 4.
#2 Done.
> Implement an Apache Camel Data Streamer
> ---------------------------------------
>
> Key: IGNITE-1790
> URL: https://issues.apache.org/jira/browse/IGNITE-1790
> Project: Ignite
> Issue Type: New Feature
> Components: streaming
> Reporter: Raúl Kripalani
> Assignee: Raúl Kripalani
> Fix For: 1.5
>
>
> An Apache Camel data streamer would make it possible for a user to use any of
> Camel's [150+ adapters/components|http://camel.apache.org/components.html] to
> consume data from the outside world and feed it into an Ignite cache.
> SOAP, REST, HTTP, WebSockets, FTP, File, XMPP, SMPP, POP3, IMAP, TCP, etc.
> This data streamer will instantiate a Camel consumer endpoint, it'll apply
> the user-specified StreamTransformer to the incoming Exchange and it'll add
> the result to the data streamer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
