Sounds good. Btw, I'd like to create a full JBI SE for scheduling, which would be based on Quartz, but would allow deployments of SUs containing jobs and schedules, but also allow creating new jobs by sending a JBI exchange on a known endpoint that the component would activate when starting. It should support transactions and persistence.
Thoughts ? On 9/26/06, Michal <[EMAIL PROTECTED]> wrote:
It would be good to run stateful jobs - I need functionality where jobs cannot run concurrently. I think it requires following changes: - QuartzComponent would need to have flag sync and if true then onJobExecute fires sendSync - instead of send - We will need a class that extends ServiceMixJob and implements StatefulJob - it would be a default jobClass if quartzComponent has flag sync equal to true cheers Michal -- View this message in context: http://www.nabble.com/QuartzComponent---running-stateful-jobs-tf2338413.html#a6506885 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
