OSGi in Action: How we use OSGi to build Open Liberty
summary
Open Liberty builds its runtime on OSGi using Equinox, declarative services, config admin and metatype-generated XML schemas to manage about 200 features expressed as subsystems-style manifests. Features map to collections of bundles, feature APIs control exports, and a runtime-created gateway bundle (dynamic-import: *) bridges legacy Java EE apps via custom classloaders. Regions enforce API visibility, shutdown requires graceful quiescing to avoid DS teardown races, and using BND for manifest generation prevents brittle hand-authored metadata.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:27Goals
- 3:25Features
- 9:12Configuration
- 12:40Schema
- 21:08Modularity
- 25:12Equinix
- 26:42Lessons learned
- 31:12Questions
related talks
35mInnovation without compromise: better, stronger, faster Java in the Cloud
43mBoost your productivity with Jakarta EE, MicroProfile & Open Liberty.
41mCloud Native Application Development with MicroProfile and Open Liberty
43mMonoliths to Modular: Navigating the Transition
55mLive Coding: Cloud native Application Development with MicroProfile & Open Liberty
28mBuilding Tools for Jakarta EE and MicroProfile Developers
39mLive Coding: cloud-native application development with MicroProfile and Open Liberty
46mModern Enterprise Java from the ground up