Hi, servicemix is using only stateless quartz jobs, but I want to prevent, that a job is started although the former instance has finsihed. Is there a reason why servicmix uses only stateless jobs or do you support it in a later release.
So I think this could be a useful feature, because stopping the whole quartz service assembly is sometimes not a practicable option. Cheers, Stephan -- View this message in context: http://www.nabble.com/Stateful-QuartzJobs-tf2913410s12049.html#a8140581 Sent from the ServiceMix - User mailing list archive at Nabble.com.
