ATopic
object encapsulates a provider-specific topic name. It is the way a client specifies the identity of a topic to JMS API methods.
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 aTopic
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 equivalentTopic
objects.
TopicSession.createTopic(String)
getTopicName() Gets the name of this topic. | |
toString() Returns a string representation of this object. |
public java.lang.StringgetTopicName() throwsJMSException
Clients that depend upon the name are not portable.
JMSException
- if the JMS provider implementation ofTopic
fails to return the topic name due to some internal error.public java.lang.StringtoString()
toString
in classjava.lang.Object