SeamFramework.orgCommunity Documentation

Weld-OSGi - Weld OSGi integration

Design specification

Mathieu Ancelin

Matthieu Clochard

Copyright © 2011 Red Hat, Inc

Preface
1. About naming and references
1.1. References
1.2. Bundle types
2. What is this specification for ?
2.1. Contracts
2.2. What is Weld-OSGi ?
2.3. Third party dependencies and environment
I. Architecture of Weld-OSGi
1. Framework organization
2. Extension part
2.1. API bundle
2.2. Extension bundle: the puppet master
3. Integration part
3.1. SPI bundle
3.2. Integration bundle: provide Weld containers
4. Weld-OSGi features
5. Weld-OSGi workflow
6. Bean bundles life cycle
7. Bean bundle characteristics
7.1. The META-INF/bean.xml file
7.2. The Embedded-CDIContainer META-INF/Manifest.MF header
II. Programming model of Weld-OSGi
8. CDI activation in bean bundles
9. Service auto publication and injection
9.1. Service bean and auto-published OSGi service description
9.2. OSGi service auto-publication with Publish annotation
9.2.1. Service type resolution
9.2.2. Service type blacklist
9.3. OSGiService annotated or Service<T> typed injection points
9.4. OSGiServiceBean and OSGiServiceProviderBean
9.5. Clearly specify a service implementation
9.5.1. Link between qualifiers and OSGi LDAP properties
9.5.2. Filter and Properties qualifiers
9.5.3. Filter and Properties stereotypes
9.5.4. Final LDAP filter
9.5.5. Using service filtering
9.6. Bean disambiguation and annotated type processing
9.6.1. Examples
9.6.2. Justification
9.7. Contextual services
9.7.1. OSGi service scopes
9.8. Required services
9.9. Inaccessible service at runtime
10. Weld-OSGi events
10.1. CDI container lifecycle events
10.2. Bundle lifecycle events
10.3. Service lifecyle events
10.4. Bean bundle required service dependency validation events
10.5. Intra and inter bundles communication events
11. OSGi facilitation
11.1. Service registry
11.2. OSGi utilities
11.3. The registration