OSGi CDI Integration Specification
summary
Spec defines how CDI maps to OSGi: publishes CDI beans as OSGi services with service types chosen by the spec, adds an @Reference analogue that supports mandatory/optional/multiple and greedy-by-default references, and maps CDI scopes to OSGi factories so dependent beans become bundle-scoped service factories or prototype factories. It layers a persistent container component under dynamic single and factory components, supports component property types and target filters, and integrates CDI portable extensions by registering them as OSGi services (extensions cannot be registered as CDI beans).
AI-written summary · about
chapters (17)
- 0:00Start
- 1:30Why CDI in OSGi?
- 6:24But DS (Declarative Services)?
- 9:19Services: singleton
- 11:44Services: bundle
- 12:14Services: prototype
- 13:01References
- 13:11Cardinality: mandatory
- 13:42Cardinality: optional
- 14:15Cardinality: multiple
- 15:48Reference Policy: reluctant
- 16:45Dynamic: mandatory
- 17:27Dynamic: optional
- 17:55Dynamic: multiple
- 18:29Components
- 22:50OSGi Logger
- 23:05Configuration
