Thanks for the excellent summary Adam. I'm not very familiar with OSGi at a deep level.
I find the point re dependency management point below pretty interesting. One of the chief reasons I'd look to using OSGi would be to allow multiple versions of the same dependency to be used by isolated modules. I don't always enjoy manually de-conflicting version incompatibilities and would prefer isolation in some cases. On Mon, Dec 15, 2014 at 2:42 AM, Adam Taft <[email protected]> wrote: > > In contrast, OSGi bundles do not traditionally include dependencies as part > of the bundle archive. Instead with OSGi, only a single copy of any common > library is maintained for the entire application framework. i.e. one and > only one copy of any commons jar is ever loaded. Additionally, OSGi > provides version conflict resolution, somewhat similar to maven conflict > resolution. OSGi benefits from reduced permgen usage loading due to these > features. > > >
