SeamFramework.orgCommunity Documentation
This document uses both CDI and OSGi specification documentations as technical references. You may refer to these documents for a better understanding of CDI and OSGi functionality, references and naming conventions. Weld-OSGi comes with other documentations and you may refer to API JavaDoc and user manual for a better understanding of Weld-OSGi.
This document discerns different bundle types for OSGi environment using Weld-OSGi:
Bundle refers to any bundle deployable in the OSGi environment as a Java
archive containing OSGi marker headers in its META-INF/Manifest.MF file.
Bean bundle refers to any bundle deployable in the OSGi environment and
managable by Weld-OSGi as a bundle containing CDI marker file
META-INF/bean.xml.
Regular bundle refers to any bundle deployable in the OSGi environment and not manageable by Weld-OSGi as a bundle not containing CDI marker file.
This specification defines:
The architecture, organization and workflow of the Weld-OSGi framework.
The programming model for, and responsibilities of, application developer who uses the Weld-OSGi framework.
The programming model for, and responsibilities of, vendor who provides the compatibility of another CDI implementation.
TODO table of content presentation
Weld-OSGi is an extension to the Weld project as a framework for developing applications in OSGi environment. Weld-OSGi aims at:
Providing a support for OSGi environments to the Weld project.
Addressing the OSGi complexity using the CDI programming model.
Weld-OSGi is a group of four bundles deployable in any OSGi environment. It allows the usage of bean bundles in these OSGi environments.
Weld-OSGi may run into an OSGi environment, therefore it requires an OSGi implementation framework to run in (such as Apache Felix, Equinox, Knopflerfish ...).
Weld-OSGi logs its operations using the SLF4J logging facade and the LogBack logging implementation.
Weld-OSGi is a part of the Weld project and may use any of the Weld project dependencies.