javax.jms.Message

Task	Complete?	Estimate	Sprint	Notes
`clearBody()`	N/A	Later		To be implemented with each message type implementation
`clearProperties()`	Mostly				2hRead/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	2h		Additional property name validation still required, valid Java identifiers etc.
`getJMSMessageID()` `setJMSMessageID(java.lang.String id)`			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)`			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	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 removedomitted.
`getJMSReplyTo()` `setJMSReplyTo(Destination replyTo)`	Yes, but -->		The current 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)`	Yes, but -->		The current 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)`
`getJMSPriority()` `setJMSPriority(int priority)`
`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)`
`getJMSType()` `setJMSType(java.lang.String type)`			4h
`acknowledge()`	Later			Part As part of implementing Client-Ack sessions.
JMSXUserId		2h		[1]
JMSXGroupID			2h	[1]
JMSXGroupSeq		2h		[1]
JMSXDeliveryCount	Later		As part of Session redelivery etc. [1]	JMSXAppID			[1] .
JMS_AMQP_TTL				[1]
JMS_AMQP_FIRST_ACQUIRER		Later		[1]
JMS_AMQP_SUBJECT	Later			[1]
JMS_AMQP_CONTENT_TYPE	Later			[1]
JMS_AMQP_CONTENT_ENCODING	Later		TODO: only on BytesMessage? [1]
JMS_AMQP_REPLY_TO_GROUP_ID			2h	[1]

[1] Handling will be required to deal with clashes where entries exist in the AMQP application-properties section with the same property name as would be used to access the relevant information which was actually carried on the AMQP header/properties. (e.g group information relating to JMSXGroupId will be carried in the AMQP properties section, so what happens when there is an application-properties entry with that key).

Phase 1: Remap-keys:

Property name prefix example: JMS_AMQP_PROP_<MANGLED>

Phase 2: Remap values.

javax.jms.TextMessage

Task	Complete?	Notes
`clearBody()`		2h	When implemented, needs to handle content-type in the case where a message was initially received and of an alternative AMQP message representation than the client defaults to sending.
`getText()`
`setText(java.lang.String string)`	Mostly		Still needs readable/writable handling

javax.jms.BytesMessage

Task	Complete?	Estimate	Sprint	Notes
`clearBody()`			2h	When implemented, needs to handle content-type in the case where a message was initially received and of an alternative AMQP message representation than the client defaults to sending.
`getBodyLength()`	Partially	1h		Only implemented for received message content so far.
`readBoolean()` `readByte()` `readBytes(byte[] value)` `readBytes(byte[] value, int length)` `readChar()` `readDouble()` `readFloat()` `readInt()` `readLong()` `readShort()` `readUnsignedByte()` `readUnsignedShort()` `readUTF()`		4h	Only implemented a very basic readBytes(byte[ ]) thus far, which still needs readable/writable handling.
`reset()`			2h
`writeBoolean(boolean value)` `writeByte(byte value)` `writeBytes(byte[] value)` `writeBytes(byte[] value, int offset, int length)` `writeChar(char value)` `writeDouble(double value)` `writeFloat(float value)` `writeInt(int value)` `writeLong(long value)` `writeObject(java.lang.Object value)` `writeShort(short value)` `writeUTF(java.lang.String value)`		4h		Only implemented a very basic writeBytes(byte[ ]) thus far, which still needs readable/writable handling.

javax.jms.ObjectMessage

Task	EstimateSprint	Notes
`clearBody()`		1h
`getObject()`	1d
`setObject(Serializable object)`		1d

javax.jms.MapMessage

Task	EstimateSprint	Notes
`clearBody()`		1h
`getBoolean(String name)` `getByte(String name)` `getBytes(String name)` `getChar(String name)` `getDouble(String name)` `getFloat(String name)` `getInt(String name)` `getLong(String name)` `getObject(String name)` `getShort(String name)` `getString(String name)`	1d
`getMapNames()` `itemExists(String name)`		1h
`setBoolean(String name, boolean value)` `setByte(String name, byte value)` `setBytes(String name, byte[] value)` `setBytes(String name, byte[] value, int offset, int length)` `setChar(String name, char value)` `setDouble(String name, double value)` `setFloat(String name, float value)` `setInt(String name, int value)` `setLong(String name, long value)` `setObject(String name, Object value)` `setShort(String name, short value)` `setString(String name, String value)`	1d

javax.jms.StreamMessage

Task	Estimate	Sprint	Notes
`clearBody()`		1h
`readBoolean()` `readByte()` `readBytes(byte[] value)` `readChar()` `readDouble()` `readFloat()` `readInt()` `readLong()` `readObject()` `readShort()` `readString()`			2d	Update mapping to output Sequences.
`reset()`	1h
`writeBoolean(boolean value)` `writeByte(byte value)` `writeBytes(byte[] value)` `writeBytes(byte[] value, int offset, int length)` `writeChar(char value)` `writeDouble(double value)` `writeFloat(float value)` `writeInt(int value)` `writeLong(long value)` `writeObject(Object value)` `writeShort(short value)` `writeString(String value)`		1d

Child pages

Versions Compared

Old Version 18

New Version Current

Key

javax.jms.Message

javax.jms.TextMessage

javax.jms.BytesMessage

javax.jms.ObjectMessage

javax.jms.MapMessage

javax.jms.StreamMessage

Child pages

Page History

Versions Compared

Old Version 18

New Version Current

Key

javax.jms.Message

javax.jms.TextMessage

javax.jms.BytesMessage

javax.jms.ObjectMessage

javax.jms.MapMessage

javax.jms.StreamMessage