...
All Iterator Pattern interface model meta-data definitions are implicitly established (not visible to TIP Interface Model projects) in the Iterator package of the TIP Framework TIP_Generator_Internal_Model sub-project.
Iterator Model Example
The The Service _ Problem _ Management is the very first of the the TIP _ Interfaces to be using the TIP _ Framework.
Its Tigerstripe model includes the following operation definitions using the Iterator interaction pattern.
The below settings define the output parameter objects as an array of ServiceProblem entity instances that can be retrieved using an iterator because it has the potential to be bulk:
...
- Refer to the TIP Framework TIP _ Soap _ Generator sub-project for XML mapping rule details - TIP_Soap_Generator_Mapping_Rules_-_Part_VI#tipOperation___BulkTransferPattern_-_Iteratordetails tipOperation: BulkTransferPattern - Iterator in TIP Soap Generator Mapping Rules - Part VI
Notifications
TIP defines a common parent for all TIP Notifications. It is called NotificationBase and shown in orange on the figures below. This type is injected by the TIP Generators into code generated from Tigerstripe Event (i.e. notification) artifacts where the 'Extends' field has been left as an empty string. It includes 1 attribute: sourceTime. Please refer to Internal Framework Model#Notifications for details.
...