I'd also vote for an OSGi backend (in the long term). It's something that has been on my mind (and mentioned) for years now.
The Nar classloader ecosystem is trying to implement features of OSGi (and doing it somewhat poorly at that, if you are honest). Not saying that OSGi is the right solution, but it's at least worth a discussion. It would be a non-trivial reboot of the entire framework though, which is the biggest downside. OSGi is very mature and has solved a lot of the problems that the Nar system attempts to solve. It's at least worth a serious consideration for NiFi 2.x. Adam On Wed, Jan 17, 2018 at 1:57 PM, Brett Ryan <[email protected]> wrote: > > > > On 18 Jan 2018, at 03:07, Matt Burgess <[email protected]> wrote: > > > > BTW, talking about mixin inheritance, shared dependencies, improved > > classloading, and module repositories, I feel like OSGi is the > > elephant in the room. I can see perfectly good reasons NOT to move to > > an OSGi-backed architecture, but it does feel like we'd end up > > implementing many of the same features and capabilities. Perhaps a > > topic for a separate DISCUSS thread? > > I did ask the same question though I wondered why you guys aren’t using > Felix specifically.
