[
https://issues.apache.org/jira/browse/NIFI-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266568#comment-15266568
]
Oleg Zhurakousky commented on NIFI-924:
---------------------------------------
I think we need to be very careful what we do here and how we address this. We
don't want to get ourself in the state where these components are hard to
maintain.
Apache Camel (http://camel.apache.org/) and Spring Integration (SI)
(http://projects.spring.io/spring-integration/) are both developer oriented EIP
frameworks. This means that the target user for them is "the coder". NiFi
primarily targets business community with its emphasis on simplicity, UI etc.
So the expectation here is that SI or Camel developers would package
application and expose it via Spring Application Context (sine both frameworks
are Spring-based) leaving DFM with a simple processor configuration step where
all they need to do is point to such package and start the processor which will
send/receive FlowFiles to/from it. This essentially gives the developers
outmost flexibility and quite frankly for Spring developer this also means that
they can write custom processors as simple POJOs (no SI, no Camel) and never
touch NiFi API if they don't want to.
As for the other features, let me address then separately
1. The number of protocol-aware endpoints is just a number since the only ones
that matter are the ones one needs (providing they also work). Also, we would
then need to explain when would one want to use FTP support from Camel or SI or
NiFi where each of the endpoints is doing the same thing.
2. Dynamic class-loading is already part of Spring Context processor, so may be
you should clarify if any functionality is missing there.
3. Dependency resolver is indeed a great feature, however may large
organizations have their own view of the world of dependencies and not "maven
friendly" when it comes to production environments, so I am afraid that feature
like this (if we ever decide to do it) would need to come with OFF button ;),
otherwise it could be looked at as an exploit.
> Add Camel support in NiFi
> -------------------------
>
> Key: NIFI-924
> URL: https://issues.apache.org/jira/browse/NIFI-924
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Jean-Baptiste Onofré
>
> I'm working on a NiFi Route able to leverage a Camel route (runtime routing),
> and another one being able to bootstrap a Camel route starting from Camel
> DSLs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
