Page History

...

getJMSReplyTo(

setJMSReplyTo(Destination replyTo)

Task	Complete?	Estimate	Notes
`clearBody()`	N/A		To be implemented with each message type implementation
`clearProperties()`	Mostly		Read/write state handling still to be added. Additional handling still 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)`	Mostly		Additional property name validation still required, valid Java identifiers etc.
`getJMSMessageID()` `setJMSMessageID(java.lang.String id)`			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)`			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		There is scope for optimizing NON_PERSISTENT messages by removing the AMQP header if all fields are at their default values and can be removed.
`getJMSDestinationgetJMSReplyTo()` `setJMSDestinationsetJMSReplyTo(Destination destination replyTo)`	Yes, but ->		The current transmission of destination-type information is rather verbose. There is scope to change this in order to significantly reduce the added per-message overhead.
`getJMSExpirationgetJMSDestination()` `setJMSExpirationsetJMSDestination(long expirationDestination destination)`	Yes, but ->		The current 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`		`getJMSMessageID()` `setJMSMessageID(java.lang.String idsetJMSExpiration(long expiration)`			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.
`getJMSPriority()` `setJMSPriority(int priority)`
`getJMSRedelivered()` `setJMSRedelivered(boolean redelivered)`			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).	)	Yes, but ->	The current transmission of destination-type information is rather verbose. There is scope to change this in order to significantly reduce the added per-message overhead .
`getJMSTimestamp()` `setJMSTimestamp(long timestamp)`
`getJMSType()` `setJMSType(java.lang.String type)`
`acknowledge()`			Part of implementing Client-Ack sessions.
JMSXUserId			[1]
JMSXGroupID			[1]
JMSXGroupSeq			[1]
JMSXDeliveryCount			[1]
JMSXAppID			[1]
JMS_AMQP_TTL			[1]
JMS_AMQP_FIRST_ACQUIRER			[1]
JMS_AMQP_SUBJECT			[1]
JMS_AMQP_CONTENT_TYPE			[1]
JMS_AMQP_CONTENT_ENCODING			[1]
JMS_AMQP_REPLY_TO_GROUP_ID			[1]

...

Child pages

Versions Compared

Old Version 17

New Version 18

Key