[
https://issues.apache.org/jira/browse/NIFI-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148927#comment-17148927
]
Matt Burgess commented on NIFI-7592:
------------------------------------
I propose to replace the need for a JettyServer (which is the NiFi class that
loads all the Web/UI WARs, etc.), we instead use its parent interface
NiFiServer, and rather than use reflection and require the need for the
nifi-jetty NAR, we instead move the NiFi JettyServer-specific code out to a
"nifi-server-nar". Then as an alternative we could add a "minifi-server-nar"
for example, that also implements NiFiServer but does similar startup code as
MiNiFi does today. The NiFi assembly would package only nifi-server-nar for
now, but later as MINIFI-422 progresses, we would have a MiNiFi assembly that
instead packages the minifi-server-nar, which doesn't require all the Web/UI
stuff.
This would allow us to replace the coupling of the web stuff with a
ServiceLoader that can search the NARs for a NiFiServer implementation. Exactly
one would be allowed, zero or more than one should result in failure to start.
> Allow NiFi to be started without a GUI/REST interface
> -----------------------------------------------------
>
> Key: NIFI-7592
> URL: https://issues.apache.org/jira/browse/NIFI-7592
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
>
> In conjunction with MINIFI-422 (bringing MiNiFi into the NiFi codebase), it
> would be necessary to allow a NiFi build to run without having the GUI and
> REST API components required. For normal NiFi releases, the GUI would be
> included in the assembly, but this Jira proposes to reorganize and refactor
> the framework code to allow NiFi to run flows and such without requiring the
> web bundle.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
