About Package Dependencies

If a package needs elements from another package to load before it can load, you must set up package dependencies. For example, you must identify package dependencies if a startup service for a package invokes a service in another package. The startup service cannot execute if the package containing the invoked service has not yet loaded.

Additionally, you should set up a package dependency if a service uses a document type from a different package as the input or output signature.

You must also identify package dependencies if Java services in a package need to access Java classes contained in another package.

Important:

Other webMethods components might include packages that register new types of elements in Designer. You should save instances of these new element types in packages that list the registering package as a package dependency. The registering package needs to load before your packages so that Designer can recognize instances of the new element type. For example, if you create new flat file schemas, you must save the flat file schemas in packages that identify the WmFlatFile package as a package dependency.