Collections provide an array-like set of administrative objects for use by the calling program. Administrative objects include tibemsQueueInfo, tibemsTopicInfo, tibemsConsumerInfo, tibemsProducerInfo, and tibemsDetailedDestStat objects.
Collections are not thread-safe and should only be operated on by a single application thread.
tibems_status tibemsCollection_Destroy(
collection has usage pointer.
Collections are created internally by the EMS library. Use tibemsCollection_Destroy to remove collections of tibemsQueueInfo, tibemsTopicInfo, tibemsConsumerInfo, and tibemsProducerInfo objects. Collections of tibemsDetailedDestStat objects cannot be directly destroyed by the user application. Attempting to destroy a tibemsDetailedDestStat object returns TIBEMS_NOT_PERMITTED.
The collection may not be directly destroyed by the application.tibems_status tibemsCollection_GetCount(
collection has usage pointer.
tibems_status tibemsCollection_GetFirst(
collection has usage pointer.
This function must be called before any calls to tibemsCollection_GetNext.tibems_status tibemsCollection_GetNext(
collection has usage pointer.
This function gets the next object in a collection. If there are no more objects in the collection, tibemsCollection_GetNext returns TIBEMS_NOT_FOUND.The function tibemsCollection_GetFirst must be called before tibemsCollection_GetNext is called for the first time.
The collection has not been initialized with a call to tibemsCollection_GetFirst.
Copyright © TIBCO Software Inc. All Rights Reserved.