Q.1.
Support for deployment of traditional .war artifacts, enable use of some of the standard Java EE libraries, provide useful defaults for many de facto standard libraries, and provide fully integrated support for Spring Dynamic Modules.

Explanation

Q.2.
OSGi doesn’t solve framework concerns, instead focusing on infrastructure requirements for Java applications.

Explanation

Q.3.
Spring Dynamic Modules was, while powerful for those already invested in an OSGi platform, not the most natural accommodations for those trying to migrate large code into the OSGi environment, SpringSource created.

Explanation

Q.4.
SpringSource dm Server many advances focus on delivering a solution, and not just a framework, for delivering:-

Explanation

Q.5.
SpringSource dm Server provides value above and beyond a regular OSGi solution.

Explanation

Q.6.
OSGi–enabling all of these interwoven dependencies via the granular use of the Import-Package header would be tedious.

Explanation

Q.7.
SpringSource dm Server also allows you to bend the rules where necessary.

Explanation

Q.8.
SpringSource dm Server works with several types of deployment formats:-

Explanation

Q.9.
Application isolation is critical because it allows you to solve the issue of reconciliation of two services whose interfaces collide. You can use:-

Explanation

Q.10.
SpringSource dm Server provides the robustness needed to commoditize enterprise application development in an OSGi environment.

Explanation

Q.11.
To begin with SpringSource dm Server but need a way to rapidly turnaround development.
Q.12.
SpringSource has provided solid tooling for Eclipse, called :-

Explanation

Q.13.
These tools—part of the broader SpringSource Tool Suite—are available as :-

Explanation