[
https://issues.apache.org/jira/browse/NIFI-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267022#comment-15267022
]
Puspendu Banerjee commented on NIFI-924:
----------------------------------------
[~ozhurakousky]
# Number of endpoint really matters because if a component is not readily
available in NiFi , we can complement that with corresponding component from
Camel. Result is wider adoption and market penetration for a relatively new
tool [ NiFi ] in Camel world.
# With Dynamic class-loading: I meant to say, using
*GroovyClassLoader.parseClass()*, it is possible to create a new Groovy class
dynamically at run-time and use it from a Groovy script or a Java application.
GroovyClassLoader.parseClass() will parse a string passed to it and attempt to
create a Groovy class. This way, it is possible to add the necessary imports,
set the class name and add the fields to the class being created. So, it will
be very useful to add/modify functionalities, support camel's groovy DSL
from/inside camel without *code-build-deploy-restart* SpringProcessor and the
result is more agile.
# Dependency resolver : I think everyone would not like to re-invent the wheel.
So, likely they will try to use something that is already established, proven.
Again, maven repo/artifactory all these are just one or another implementation,
it could be any other sort of repo structure, you just need to code a resolver
for that. Can you please name some widely adopted CI tool which does not
support maven repository structured data and any repo which can con prevent
unauthorized access by some means.
Again,for success _[ adoption/ market penetration/ sustainability ] of a
product we should think about re-utilizing existing resources, shorter learning
curve in turn avoid additional cost burden._ For example, when I present a demo
[ pre-sales, training etc.], I see a large audience is techie[ skilled with
DataStage, Fuse ESB, DataPower, other Drag-Drop tools with little programming
etc.] and Subject Matter Expert but not a Spring developer. So, ensuring that
NiFi is easy to adopt & will not disturb current eco-system is a key.
----
[~joewitt]
Good to know that you have a good sense of humor :D. Seems it has started to
bloom at this Spring!
h3. LOL
- Larger Dependency situation can be handled by dependency resolver on as and
when basis, because all dependencies for camel routes should only have run-time
scope and defined at corresponding Camel/SI processor instance.
> 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)
