jsr343-experts@jms-spec.java.net

[jsr343-experts] Re: (JMS_SPEC-34) Calling setJMSDeliveryMode or setJMSPriority on a javax.jms.Message before it is sent don't have any effect

From: Nigel Deakin <nigel.deakin_at_oracle.com>
Date: Thu, 22 Dec 2011 16:50:23 +0000

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

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 change affects the javadoc comments for the following methods on Message:

setJMSDeliveryMode
setJMSExpiration
setJMSPriority
setJMSMessageID
setJMSTimestamp
setJMSRedelivered
setJMSDeliveryTime (proposed in JMS_SPEC-44)

Currently the javadoc comments for these methods simply states:

     /** Sets the message's [name of property] value
       *
       * <P>JMS providers set this field when a message is sent. This method
       * can be used to change the value for a message that has been received.

These have been changed as follows:

    /** Sets the message's [name of property] value.
      *
      * <P>This method is for use by JMS providers only to set this field
      * when a message is sent. This message cannot be used by clients
      * to configure the [describe feature] of the message. This method is public
      * to allow one JMS provider to set this field when sending a message
      * whose implementation is not its own.

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:

Section 3.4.1 "How Message Header Values Are Set" has been updated.

Section 11.5.8. "Clarification: message headers that are intended to be set by the JMS provder" is the changelog for
this issue.

Nigel