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

View solution

Q. To create services and have those automatically installed in the registry.

View solution

Q. Element to export the bean as an OSGi service, classified by the interface we specify.

View solution

Q. An anonymous bean specified inside of the osgi:service element allows you to avoid cluttering the namespace.

View solution

Q. The first, most direct connection to OSGi is the bean that’s created on your behalf when you export a service. This bean, an instance of:-

View solution

Q. By default, beans created in a Spring application context are global to the entire OSGi runtime.

View solution

Q. Sometimes, you may want to limit the visibility of a service so that multiple clients each get their own instance of the bean.

View solution

Q. Spring Dynamic Modules also supports injection and manipulation of bundles themselves. An injected bundle is of type:-

View solution

Q. Once acquired, the Bundle can be interrogated to introspect information about the bundle itself, including any entries, its current state.

View solution

Q. OSGi will let you maintain multiple versions of a service in your registry at the same time.

View solution

Q. Multiple services of the same interface may be registered inside of an OSGi environment, which necessitates a conflict-resolution process.

View solution

Q. When specified on a service element, allows the ascription of a rank relative to other beans with the same interface.

View solution

Q. A more robust solution to service discrimination is service attributes.

View solution

Q. There are frequently situations where OSGi will return more than one instance of a service that satisfies the interface.

View solution

Q. Attribute, which, is the symbolic name of another bundle.

View solution

Q. 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.

View solution

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

View solution

Q. 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.

View solution

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

View solution

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

View solution