Contained types

Contained types make it possible to reference items that are contained within the body of another item.

Examples of contained types include: Xoom internally assigns each contained item an identity such that it can be referenced. That identity will not appear in XoomXML.


Here is a screenshot of the References Report. This report lists every item together with its dependencies. ABCapacityLimits Property[District], highlighted in red, is listed as an item but is actually contained within the body of another item, Collection[ABCapacityLimits]].

Screenshot from the references report showing an item that exists below the third level

We can see this more clearly when we look at the XoomXML. The item (highlighted in red) is contained within the body of Collection[ABCapacityLimits], (highlighted in blue):

The Xoom identity goes to the parent node at the third level: Collection[ABCapacityLimits] (highlighted in blue). Assigning the contained item the workaround identity, ABCapacityLimits Property[District], means that it can be referenced, hence it appears in the References Report. The workaround identity does not appear in XoomXML.
Note: Xoom names nodes according to the internal representation of Service Optimization, hence 'Attributes' are what Service Optimization user interfaces refer to as 'Properties'.

The use of contained types makes it possible to deploy changes to contained items using xoom:set special form.