Creates a durable subscriber to the specified topic.

If a client needs to receive all the messages published on a topic, including the ones published while the subscriber is inactive, it uses a durable TopicSubscriber. The JMS provider retains a record of this durable subscription and insures that all messages from the topic's publishers are retained until they are acknowledged by this durable subscriber or they have expired.

Sessions with durable subscribers must always provide the same client identifier. In addition, each client must specify a name that uniquely identifies (within client identifier) each durable subscription it creates. Only one session at a time can have a TopicSubscriber for a particular durable subscription.

A client can change an existing durable subscription by creating a durable TopicSubscriber with the same name and a new topic and/or message selector. Changing a durable subscriber is equivalent to unsubscribing (deleting) the old one and creating a new one.

In some cases, a connection may both publish and subscribe to a topic. The subscriber NoLocal attribute allows a subscriber to inhibit the delivery of messages published by its own connection. The default value for this attribute is false.

Namespace:  Kaazing.JMS
Assembly:  Kaazing.JMS (in Kaazing.JMS.dll)

Syntax

Visual Basic
Function CreateDurableSubscriber ( _
	topic As ITopic, _
	name As String _
) As ITopicSubscriber
C#
ITopicSubscriber CreateDurableSubscriber(
	ITopic topic,
	string name
)
Visual C++
ITopicSubscriber^ CreateDurableSubscriber(
	ITopic^ topic, 
	String^ name
)

Parameters

topic
Type: Kaazing.JMS..::..ITopic
the non-temporary Topic to subscribe to
name
Type: System..::..String
the name used to identify this subscription

Implements

ISession..::..CreateDurableSubscriber(ITopic, String)

Exceptions

ExceptionCondition
Kaazing.JMS..::..JMSExceptionif the session fails to create a subscriber due to some internal error.
Kaazing.JMS..::..InvalidDestinationExceptionif an invalid topic is specified.

See Also