[
https://issues.apache.org/jira/browse/NIFI-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266593#comment-15266593
]
Joseph Witt commented on NIFI-924:
----------------------------------
Just wanted to mention that this statement "NiFi primarily targets business
community with its emphasis on simplicity, UI etc." does not really reflect the
intent behind NiFi and certainly not within this open source developer driven
community.
>From the beginning NiFi was about "How can I as a developer and operations
>oriented person get my job done faster and how can I make what has been built
>and configured more understandable and accessible to others"
This is a really important message as it starts with the developer and is meant
to include others - in short it is to increase shared understanding.
Back to the topic at hand:
- I think the SpringContext processors that were made available are a great
start and I think [[email protected]] agreed which is why he pulled
back his PR and made supportive commentary. However, there is still value in
exploring a more direct NiFi and Camel integration as long as that is what
motivated and capable parties would like to do. We don't really have to be
that careful here. Extensions have for always and ever been a 'let a thousand
flowers bloom' thing. They are good and useful if some group of people use
them and get what they need from them. It is in the core framework that we
need to be more careful. Now, i do think this could create some large
dependency situations and for that we must hurry up and get this registry in
play. Right now we're putting 1000 flowers in a small flower bed but it the
registry would give us a large field and that is what we need. Spring /
flowers / Spring context? Can I get an lol here?
> 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)
