...
javax.jms.Message
Task | Complete? | Estimate | Sprint | Notes | ||||
---|---|---|---|---|---|---|---|---|
clearBody() | N/ALater | 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. | ||||||
| Mostly | Additional property name validation still required, valid Java identifiers etc. | ||||||
| 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.
Define mapping for type conversion. Write Up. (1d 4h) Parser. (2d) Annotation handling.(4h) | ||||||
setJMSCorrelationID(java.lang.String correlationID)
| 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. | |||||
| 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. | ||||||
| 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. | ||||||
| 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. | ||||||
| ||||||||
| ||||||||
| 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). | ||||||
| ||||||||
| ||||||||
acknowledge() | Later | As part of implementing Client-Ack sessions. | ||||||
JMSXUserId | [1] | |||||||
JMSXGroupID | [1] | |||||||
JMSXGroupSeq | [1] | |||||||
JMSXDeliveryCount | Later | [1]. As part of Session redelivery etc. JMSXAppID | 2h | [1]. | ||||
JMS_AMQP_TTL | [1] | |||||||
JMS_AMQP_FIRST_ACQUIRER | 2hLater | [1] | ||||||
JMS_AMQP_SUBJECT | Later | 2h | [1] | |||||
JMS_AMQP_CONTENT_TYPE | Later | 2h | [1] | |||||
JMS_AMQP_CONTENT_ENCODING | 2hLater | [1] TODO: only on BytesMessage? [1] | ||||||
JMS_AMQP_REPLY_TO_GROUP_ID | [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>
...
javax.jms.TextMessage
Task | Complete? | Estimate | Sprint | Notes |
---|---|---|---|---|
| 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 |
---|---|---|---|---|
| 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 | 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() |
Only implemented a very basic readBytes(byte[ ]) thus far, which still needs readable/writable handling.
| |||
reset() | ||||
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) | Partially | Only implemented a very basic writeBytes(byte[ ]) thus far, which still needs readable/writable handling. |
javax.jms.ObjectMessage
Task | Complete? | Estimate | Sprint | Notes |
---|---|---|---|---|
| 1h |
|
| |
getObject() | 1d | |||
setObject(Serializable object) | 1d |
javax.jms.MapMessage
Task | Complete? | EstimateSprint | Notes | |
---|---|---|---|---|
| 1h | |||
| 1d | |||
| 1h | |||
| 1d |
javax.jms.StreamMessage
Task | Complete? | EstimateSprint | Notes | |
---|---|---|---|---|
| 1h | |||
| 2d | Update mapping to output Sequences. | ||
reset() | 1h | |||
| 1d |