Bundle Publisher Dependency Graphs

Designing and Implementing Composite Applications : webMethods Application Platform User’s Guide : Developing with Application Platform in Designer : About Managing Project Dependencies : Bundle Publisher View : Bundle Publisher Dependency Graphs

Examples of Dependency Validation

The Bundle Publisher provides you with a dialog, which displays potential warnings and errors that are discovered when validating a collection of bundles. The Bundle Publisher determines the dependencies between the bundles by examining all of the OSGi manifests and Bnd templates in the group of bundles. Based on the examination, the Bundle Publisher forms a dependency graph. When you start the server, all active bundles are also included in the graph, unless you have removed them.

When creating a dependency graph for a group of bundles, the Bundle Publisher validates the attempts for:

Publishing a bundle that exports the same package and version.

Publishing a bundle that imports a package that is not exported. Note that you can configure the Bundle Publisher to ignore optional missing imports, like bundles with package imports that contain the following qualifier: resolution:=optional.

Unpublishing a bundle that exports a package imported by another bundle.

Unpublishing a bundle that is required by one or more published bundles.

Publishing a bundle that produces a circular dependency.

The Bundle Publisher can display the following types of messages:

Message Type	Description
Information	Status messages that provide information.
Warning	Messages that indicate dependency issues that may prevent bundles from reaching an active state.
Error	Messages that indicate invalid bundles. For example, an error message can indicate that there is a corrupt file or a jar with an invalid OSGi manifest.

Contact Support | Community | Feedback