[
https://issues.apache.org/jira/browse/CAMEL-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984023#action_12984023
]
Hadrian Zbarcea commented on CAMEL-913:
---------------------------------------
I don't really understand the use case.
My questions are:
1. What is the relationship between the initial message sent to the timer
endpoint and the subsequent messages sent by the timer? Is it the same message
or the timer send empty messages as the timer consumers do now?
2. For one message sent to the timer endpoint, how many messages are sent later
by the timer?
3. What is the difference between this and starting a new route in response to
the message sent?
{code}
from("quartz://myGroup/myTimer?trigger.repeatInterval=2000&trigger.repeatCount=1")
.to("jms:topic:SomeTopic");
{code}
4. How will exceptions be handled if sending to the endpoint fails? Is the
message in-only or in-out?
5. Are transactions supported?
The particular example above could be handled with a combination of
[loop|http://camel.apache.org/loop.html] and
[delayer|http://camel.apache.org/delayer.html].
> sending a message to a timer or quartz endpoint should create a new timer -
> which when it fires, a message is sent to an endpoint specified by a header.
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-913
> URL: https://issues.apache.org/jira/browse/CAMEL-913
> Project: Camel
> Issue Type: Improvement
> Reporter: james strachan
> Fix For: Future
>
>
> e.g. if you sent a message with headers
> {code}
> CamelReplyTo = activemq:cheese
> CamelTimerDelay = 1000
> {code}
> it'd send a message to activemq:cheese in a second
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
