Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TaskComplete?EstimateSprintNotes
clearBody()Later N/A To be implemented with each message type implementation
clearProperties()(tick)2h 

Additional handling to be added for custom vendor properties as they are individually implemented.

getPropertyNames()

propertyExists(java.lang.String name)

getBooleanProperty(java.lang.String name)

getByteProperty(java.lang.String name)

getDoubleProperty(java.lang.String name)

getFloatProperty(java.lang.String name)

getIntProperty(java.lang.String name)

getLongProperty(java.lang.String name)

getObjectProperty(java.lang.String name)

getShortProperty(java.lang.String name)

getStringProperty(java.lang.String name)

setBooleanProperty(java.lang.String name, boolean value)

setByteProperty(java.lang.String name, byte value)

setDoubleProperty(java.lang.String name, double value)

setFloatProperty(java.lang.String name, float value)

setIntProperty(java.lang.String name, int value)

setLongProperty(java.lang.String name, long value)
setObjectProperty(java.lang.String name, java.lang.Object value)
setShortProperty(java.lang.String name, short value)
setStringProperty(java.lang.String name, java.lang.String value)

(tick)2h  

getJMSMessageID()

setJMSMessageID(java.lang.String id)

(tick)1d 

Requires an encoding/decoding scheme to be developed to allow retaining the underlying type information, as AMQP message-ids/correlation-ids can be a number of different types.

getJMSCorrelationID()

getJMSCorrelationIDAsBytes()

setJMSCorrelationID(java.lang.String correlationID)

setJMSCorrelationIDAsBytes(byte[] correlationID)

(tick)4d Requires an encoding/decoding scheme to be developed to allow retaining the underlying type information, as AMQP message-ids/correlation-ids can be a number of different types.

getJMSDeliveryMode()

setJMSDeliveryMode(int deliveryMode)

Mostly (tick) but -->
  There is still scope for optimizing NON_PERSISTENT messages by removing the AMQP header if all fields are at their default values and can be omitted.

getJMSReplyTo()

setJMSReplyTo(Destination replyTo)

(tick) but -->  The prototypes transmission of destination-type information is rather verbose. There is scope to change this in order to significantly reduce the added per-message overhead.

getJMSDestination()

setJMSDestination(Destination destination)

(tick) but -->  The prototypes transmission of destination-type information is rather verbose. There is scope to change this in order to significantly reduce the added per-message overhead.

getJMSExpiration()

setJMSExpiration(long expiration)

(tick)   

getJMSPriority()

setJMSPriority(int priority)

(tick)   

getJMSRedelivered()

setJMSRedelivered(boolean redelivered)

Later  

Somewhat dependant on implementing AMQP delivery-count header handling.

setJMSRelivered makes no sense as the spec explicitly says you dont use it when sending messages (yours or foreign).

getJMSTimestamp()

setJMSTimestamp(long timestamp)

(tick)   

getJMSType()

setJMSType(java.lang.String type)

(tick)4h  
acknowledge()Later  As part of implementing Client-Ack sessions.
JMSXUserId 2h [1]
JMSXGroupID 2h [1]
JMSXGroupSeq 2h [1]
JMSXDeliveryCountLater  [1]. As part of Session redelivery etc.
JMSXAppID 2h [1]
JMS_AMQP_TTL(tick)  [1]
JMS_AMQP_FIRST_ACQUIRER 2h [1]
JMS_AMQP_SUBJECT 2h [1]
JMS_AMQP_CONTENT_TYPE 2h [1]
JMS_AMQP_CONTENT_ENCODING 2h [1] TODO: only on BytesMessage?
JMS_AMQP_REPLY_TO_GROUP_ID 2h [1]

...