[jira] [Created] (NIFI-6235) JettyServer Loads content viewers in arbitrary order

["Jeffrey Ripps (JIRA)" <ji...@apache.org>]

Jeffrey Ripps created NIFI-6235:
-----------------------------------

             Summary: JettyServer Loads content viewers in arbitrary order
                 Key: NIFI-6235
                 URL: https://issues.apache.org/jira/browse/NIFI-6235
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core UI, Extensions
    Affects Versions: 1.9.2
            Reporter: Jeffrey Ripps


The org.apache.nifi.web.server.JettyServer creates a map of "otherWars" which is where both the nifi-standard-content-viewer and other custom content viewers are placed when nifi loads. 

Then in the loadWars method a map called mimeMappings is created.  This is where the servletContext will go to lookup, for a given mime-type flowfile attribute, which content-viewer to point to.  Because everything is iterated over as a set, the order with which these content-viewer wars is loaded becomes arbitrary and inconsistent.  

Nifi should either decide that it wants to enforce loading its own standard content viewer last and therefor force known mime types to be viewed in the standard viewer OR (and this is what I would think would make the most sense) ensure the nifi-standard-content-viewer is loaded first and therefore custom content viewers in other nars can create custom viewers that will be directed to instead of the standard content viewer for a given mimeType listed in their own META-INF/nifi-content-viewer file.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)