Q.1.
OSGi—which was formerly known as the:-

Explanation

Q.2.
OSGi provides a layer on top of the JVM’s default class loader.

Explanation

Q.3.
On top of Spring Dynamic Modules, SpringSource built SpringSource dm Server, which is a server wired from top to bottom with OSGi and Spring.

Explanation

Q.4.
OSGi is a framework.

Explanation

Q.5.
User component models are:-

Explanation

Q.6.
In OSGi, anything used by something else is a state.

Explanation

Q.7.
“Service” doesn’t imply any:-

Explanation

Q.8.
OSGi bundles are simply standard .jar files with customized MANIFESTs that OSGi consumes at runtime.

Explanation

Q.9.
Tool which dynamically interrogates classes for their imports and generates OSGi–compliant entries.

Explanation

Q.10.
The plug-in produces OSGi–compliant bundles that work in any container.

Explanation

Q.11.
The Bundle-Activator directive describes to the OSGi environment, which class implements :-

Explanation

Q.12.
When the bundle begins to load and start, it calls the start method of the:-

Explanation

Q.13.
To start using Spring to smooth over some of the minutiae of resource acquisition and to help build more reliable systems in an OSGi environment.

Explanation

Q.14.
Spring Dynamic Modules scans our deployed bundles and loads an ApplicationContext (actually, the specific type of the ApplicationContext is OsgiBundleXmlApplicationContext) into memory based on an event, or a trigger.

Explanation

Q.15.
You’ll split your OSGi–specific Spring configuration and your plain-vanilla Spring configuration into:-

Explanation