users@jms-spec.java.net

[jms-spec users] [jsr343-experts] Re: (JMS_SPEC-39) Make clientId optional when creating a durable subscription

From: Nigel Deakin <nigel.deakin_at_oracle.com>
Date: Wed, 21 Dec 2011 18:41:35 +0000

http://java.net/jira/browse/JMS_SPEC-39

There were no objections to this proposal when it was raised some time ago.

I've now updated the javadocs and the draft spec with this change (these changes are additive, so those docs include
other changes).

As with all these updates, I've summarised the changes in three places: this email, in the JIRA issue, or in the
changelog at the bottom of the spec document itself.

The updated Javadocs are here:
http://java.net/projects/jms-spec/sources/repository/content/jms2.0/target/jms-2.0-javadoc.jar

The only changes are to comments, not to the API. The updated comments as follows:

On the Session interface the javadocs for the two createDurableSubscriber methods and the unsubscribe method have been
rewritten.

On the proposed MessagingContext interface the javadocs for the two createSyncDurableSubscriber methods, the two
setMessageListener methods used to create durable subscriptions, the two setBatchMessageListener methods used to create
durable subscriptions and the unsubscribe method have been rewritten.

The updated draft spec is here:
http://java.net/projects/jms-spec/sources/repository/content/jms2.0/specification/word/JMS20.pdf
All changes are hightlighted. The changes made for this issue are as follows:

In JMS 2.0 it is no longer mandatory for the client identifier to be set when creating or activating a durable
subscription. The following changes have been updated to reflect this change:

Section 4.3.2 "Client Identifier" has been changed to state that its use in identifying a durable subscription is optional.

Section 6.3 "Durable Subscription" has been amended by adding a cross-reference to Section 6.11.1 "Durable
TopicSubscriber" at the end.

Section 6.11.1 "Durable TopicSubscriber" has been completely rewritten. This section was essentially a copy of the
javadoc comment on the createDurableSubscriber methods and since those javadoc comments have been rewritten to make them
clearer this section has been rewritten as well.

The only substantive change is to state that the use of client identifier in identifying a durable subscription is
optional. Cross-references to Section 6.3 "Durable Subscription" and Section 4.3.2 "Client Identifier" have been added
at the end.

Section 11.5.7. Durable subscriptions has been added, which is a change log.