...
Task | Complete? | Estimate | Sprint | 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. | ||
| Mostly | Additional property name validation still required, valid Java identifiers etc. | ||
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. | |||
| 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. | ||
| 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. | ||
| ||||
| 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. | |||
| ||||
| 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. | ||
| ||||
| ||||
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] |
...