[
https://issues.apache.org/jira/browse/ARTEMIS-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615560#comment-15615560
]
Robbie Gemmell edited comment on ARTEMIS-821 at 10/28/16 2:27 PM:
------------------------------------------------------------------
JMS 2.0 takes a relative delay for the producer on the set call, but the value
you actually set/get with the messages once sent is 'absolute' (its still
relative to the epoch in the end ;)).
was (Author: gemmellr):
JMS 2.0 takes a relative delay for the producer on the send call, but the value
you actually set/get with the messages once sent is 'absolute' (its still
relative to the epoch in the end ;)).
> Support scheduled messages with the STOMP protocol
> --------------------------------------------------
>
> Key: ARTEMIS-821
> URL: https://issues.apache.org/jira/browse/ARTEMIS-821
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 1.4.0
> Reporter: Jiri Danek
> Priority: Blocker
> Fix For: 1.5.0
>
>
> Scheduled messages are already supported with Core and with AMQP. Scheduled
> messages are JMS 2.0 feature.
> I would like to request their support in STOMP protocol. This feature has
> been also requested in [a Stack Overflow
> question|http://stackoverflow.com/q/38996576/6081394].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
