I am not sure what you are trying to do, it would help to post your
route.
The quarz component provides the mechanism to trigger an event at
predetermined moments of time, which will cause some things to happen,
like a crontab job. Actually even the syntax is very similar to
crontab. If you use Windows, it's sorta like the AT command.
Since this triggers an event, it makes no sense to send a message to
it. What I think you want to do is do some processing both at
predetermined times *and* on demand, in which case you can do
something like:
from("quarz:...", "direct:start").do-whaterver-you-want(...);
and then your route will be triggered both by quartz and by you
sending a message to the direct:start endpoint. You could use seda or
jms (instead of direct) for asynchronous processing, what is best
depends on your application.
Cheers,
Hadrian
On Jun 18, 2009, at 1:27 PM, sriramch wrote:
I have defined a Quartz endpoint which I'd also like to from an on-
demand
service (outside the schedule defined by the Quartz endpoint
configuration).
However when I try this using ProducerTemplate:sendBody method, I
get an
exception that says 'You cannot send messages to this endpoint'. Is
there
any reason why the quartz end-point is built in this fashion. I can
get the
functionality I want by breaking up my route, but that would mean
unnecessarily complicating the route definitions. Is there any other
way for
me to invoke the Quartz endpoint on demand?
Thanks,
Sriram
--
View this message in context:
http://www.nabble.com/Executing-a-Quartz-Endpoint-on-demand-tp24095337p24095337.html
Sent from the Camel - Users mailing list archive at Nabble.com.
