Case 5: Server Package Hierarchy with Nested Structure Packages 

 

Description

The top-level server structure package SP2 (see figure below) offers a

• Filter package interface FILTER_2 and
• Virtual standard package interface VIRT_DEF_2.

The first-level server structure package SP21 provides the filter package interface FILTER_21 and the second-level structure package SP211 the filter package interface FILTER_211. 

The structure package SP211 contains a regular development package P2111 that exposes  repository objects using the package interface PINF2111. The development package P2111 serves as the actual server package for client package P111 from another package hierarchy.

 

Solution

To be able to use visible repository objects from the server package hierarchy, the client structure package has to declare a use access for the filter package interface FILTER_2 that is defined at the server structure package level.

To declare a use access to one of the first packages that are not structure packages - below the root structure package SP2 - all the structure packages in between (here: SP21 and SP211) do not need to be considered. In other words: The client package can ignore the nested structure packages below the root structure package.

 

All package interfaces of the main or development packages (here: P2111) that are direct subpackages of the lowest-level structure package (here: SP211) are directly visible for other package hierarchies. To use content that is exposed in the package interface PINF2111 of the server package P2111, the respective client package and all its superpackages - up to the level of the client structure package SP1 – have to declare a use access for that package interface.