Class InitialRemoteIteratorData<T>

All Implemented Interfaces:
Serializable
Direct Known Subclasses:
AsInitialRemoteIteratorData, EcInitialRemoteIteratorData, EntityInitialRemoteIteratorData, EntityInitialRemoteIteratorData, ErrorDataInitialRemoteIteratorData, ExecHistEntryInitialRemoteIteratorData, IdUdtInitialRemoteIteratorData, IdvInitialRemoteIteratorData, InstIdInitialRemoteIteratorData, InstIdPairInitialRemoteIteratorData, InstInitialRemoteIteratorData, InstRefInitialRemoteIteratorData, InstStatusInitialRemoteIteratorData, NamespaceInitialRemoteIteratorData, NsInitialRemoteIteratorData, QaInitialRemoteIteratorData, RaInitialRemoteIteratorData, ResInitialRemoteIteratorData, ResInstInitialRemoteIteratorData, ScInitialRemoteIteratorData, TemplIdInitialRemoteIteratorData, TemplInitialRemoteIteratorData, TemplKindInitialRemoteIteratorData, TemplRefInitialRemoteIteratorData, TemplStatusInitialRemoteIteratorData, TtdeInitialRemoteIteratorData, WorkHistEntryInitialRemoteIteratorData

public abstract class InitialRemoteIteratorData<T> extends AbstractListRemoteIteratorData<T>
Parent class for all initial remote iterator data. This separates the initial remote iterator data class hierarchy from the following (non-initial) remote iterator data class hierarchy.

When referring to this class from the web service API, make sure that only the iterator data relevant for one specific service is created. Since this class refers to all subclasses, irrelevant data may be created for a service. For instance the ScRemoteIteratorData may become part of the org model manager which uses QaRemoteIteratorData only. This leads to quite some additional classes becoming part of the service, e. g. IncompleteSessionContext, DataContext, and ActivityInstance.

See Also:
  • Field Details

    • snapshot

      @NotNull public @NotNull Boolean snapshot
    • forwardOnly

      @NotNull public @NotNull Boolean forwardOnly
  • Constructor Details

    • InitialRemoteIteratorData

      public InitialRemoteIteratorData()