You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nifi.apache.org by "Puspendu Banerjee (JIRA)" <ji...@apache.org> on 2016/04/30 04:16:12 UTC

[jira] [Issue Comment Deleted] (NIFI-924) Add Camel support in NiFi

     [ https://issues.apache.org/jira/browse/NIFI-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Puspendu Banerjee updated NIFI-924:
-----------------------------------
    Comment: was deleted

(was: [~mattf] & [~joewitt] I completely support the vision of 
    1.Spring independence [ as camel supports blueprint, Java configurations [ DSL] too]
as well as the implementation of camel integration should is in such a way that a 
    2. dynamic classloader[ ex: groovy based] can load all  dependencies as required by camel routes '
    3. and a dependency resolver is capable of downloading dependency from maven compatible repositories if not present in classpath 

In case there is any plan for such implementation as part of standard distribution, it will be excellent! and a working sample for #2 & #3 is available.
[~dkjerrumgaard] [~jbonofre] In case you have any vision to put in. )

> 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)