[ http://jira.jboss.com/jira/browse/JBMESSAGING-1203?page=all ] Tim Fox updated JBMESSAGING-1203: --------------------------------- Fix Version/s: 2.0.0 Beta -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1203?page=com.atlassian.ji... ] Andy Taylor reassigned JBMESSAGING-1203: ---------------------------------------- Assignee: Andy Taylor (was: Tim Fox) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1203?page=com.atlassian.ji... ] Tim Fox commented on JBMESSAGING-1203: -------------------------------------- I don't like the idea of putting it on the message since this is not a major use case and we don't want to add extra size to the message for the 99.99% of cases that won't use it. You don't need it on the message to be able to persist the information. Just add an update record for the scheduled delivery time where appropriate. If you look in JournalStorageManager there's already a TODO for this: case SET_SCHEDULED_DELIVERY_TIME: { // TODO } And the constant already exists -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira