Thanks for the confirmation. I added a section on Migrating to 2.5.0 [1] mentioning the simplified Java Servlet implementation pattern as the recommended approach for custom Content Viewers.
Regards, David Handermann [1] https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance#MigrationGuidance-Migratingto2.5.0 On Wed, Aug 20, 2025 at 2:32 PM Mark Bean <mark.o.b...@gmail.com> wrote: > > Yes, our implementation of the custom content viewer followed the pattern > of the standard content viewer. We implemented a SpringBootApplication just > as previously NiFi had StandardContentViewerApplication.java along with a > corresponding Spring-based controller. > > Thanks, > Mark > > > On Wed, Aug 20, 2025 at 1:43 PM David Handermann < > exceptionfact...@apache.org> wrote: > > > Mark, > > > > Thanks for raising the question in light of the changes. Although the > > change for NIFI-14657 was more of an implementation detail, it is > > certainly the recommended pattern. > > > > For clarification, did you run into similar Spring dependency issues? > > That would help clarify what should be noted. > > > > Regards, > > David Handermann > > > > On Wed, Aug 20, 2025 at 12:23 PM Mark Bean <mark.o.b...@gmail.com> wrote: > > > > > > I noticed that version 2.5.0 introduced a change in how the servlet > > context > > > is accessed for the content viewer. Since we have a custom content > > viewer, > > > we needed to make some updates due to the changes under NIFI-14657 [1]. > > > > > > Would it be possible to add a note about the removal of Spring Boot in > > the > > > content viewer (and custom extensions) to the migration guidance for > > 2.5.0 > > > [2]? I think this would be really helpful for others making similar > > updates. > > > > > > Thanks, > > > Mark > > > > > > [1] https://issues.apache.org/jira/browse/NIFI-14657 > > > [2] https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance > >
