...
Task | Complete? | Estimate | Sprint | Notes | |||||
---|---|---|---|---|---|---|---|---|---|
clearBody() | Later | To be implemented with each message type implementation | |||||||
clearProperties() | Additional handling to be added for custom vendor properties as they are individually implemented. | ||||||||
| |||||||||
| 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. | ||||||||
setJMSCorrelationID(java.lang.String 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. | ||||||||
| 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. | |||||||
| 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. | |||||||
| 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. | |||||||
| |||||||||
| |||||||||
| 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 | 2h | [1] | |||||||
JMS_AMQP_SUBJECT | 2h | [1] | |||||||
JMS_AMQP_CONTENT_TYPE | 4h | [1] | |||||||
JMS_AMQP_CONTENT_ENCODING | 4h | [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.
...