ITopic object encapsulates a provider-specific topic name. It is the way a client specifies the identity of a topic to JMS API methods. For those methods that use a IDestination as a parameter, a ITopic object may used as an argument . For example, a ITopic can be used to create a IMessageConsumer and a IMessageProducer by calling: ISession.CreateConsumer(IDestination destination)ISession.CreateProducer(IDestination destination)Many publish/subscribe (pub/sub) providers group topics into hierarchies and provide various options for subscribing to parts of the hierarchy. The JMS API places no restriction on what a ITopic object represents. It may be a leaf in a topic hierarchy, or it may be a larger part of the hierarchy.
The organization of topics and the granularity of subscriptions to them is an important part of a pub/sub application's architecture. The JMS API does not specify a policy for how this should be done. If an application takes advantage of a provider-specific topic-grouping mechanism, it should document this. If the application is installed using a different provider, it is the job of the administrator to construct an equivalent topic architecture and create equivalent ITopic objects.
For a list of all members of this type, see ITopic Members.
Namespace: WebLogic.Messaging
Assembly: WebLogic.Messaging (in WebLogic.Messaging.dll)
ITopic Members | WebLogic.Messaging Namespace | CreateConsumer(IDestination) | CreateProducer(IDestination)