[NIFI-1571] Provide generic processor that would bootstrap itself from Spring's Application Context

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.6.0
• Assignee: Oleg Zhurakousky
• Reporter: Oleg Zhurakousky
• Created: 26/Feb/16 13:45
• Updated: 04/May/16 21:52
• Resolved: 18/Mar/16 03:50

Description

So, several clients have expressed interests in using WorkFlow orchestration frameworks such as Camel, Spring Integration etc. to be able to encapsulate yet modularize and externalize the complexity of some of the custom processors as well as handle some of the use cases that fall outside of scope of Data Flow paradigm (e.g., transactional context and XA between two+ Processors).
There is already a ticket to provide Camel support - NIFI-924. However realizing that both Camel and naturally Spring Integration is based on Spring Application Context it appears that instead of having multiple extensions we should have a more generic extension for a Processor that would delegate its processing to a bean in provided Spring Application Context (AC). This way AC becomes a black box and could contain anything (e.g., Camel, Spring Integration or some custom user code).

Issue Links

• incorporates: NIFI-1647 Spring context processor usability issue
• relates to: NIFI-924 Add Camel support in NiFi
• relates to: NIFI-1842 implement GetWithCamel and PutWithCamel processors, as selectable-endpoint connectors