Show TOC

 Case 2: Using Standard Package InterfaceLocate this document in the navigation structure

 

Description

Let's assume that a server structure package provides a standard package interface. There are no other package interfaces defined in this structure package.

 

Solution

To use the repository objects that are exposed in the standard package interface, the respective client package and all its superpackages - up to the level of the structure client package - have to declare a use access to that standard package interface. 

 

 

The above graphic clarifies how the usage of the standard package interface is linked to use access to be declared on the client-side package hierarchy: 

SP1 and SP2 are two structure packages and form the root of two different package hierarchies. SP1 acts as a client structure package. It contains a main package MP11, which itself contains a regular development package P111. The actual client package P1111 is a subpackage of the P111. SP2 acts as a server structure package for SP1 and provides a standard package interface DEFAULT_2 only. This interface makes visible all the repository objects that are defined in its subpackages.

In order for the client package P1111 to be able to use the content from SP2 (that is defined in one of its subpackages), the actual client package and all its superpackages have to declare use access to the standard interface of SP2. In other words: the standard interface DEFAULT_2 has to be entered in P1111, P111, MP11, and in SP1 to declare use access to all non-encapsulated subpackages of SP2.