On Tue, 9 Nov 2004, Vadim Gritsenko wrote:
Vadim Gritsenko wrote:
[EMAIL PROTECTED] wrote:
DirectSchedulerFactory.getInstance().createScheduler(DEFAULT_QUARTZ_SCHEDULER_NAME
+ runID, runID, pool, store);
IMHO, it should cause problem with JDBC job store, and with clustered
Cocoon servers also. Point of JDBC store is to coordinate cron jobs
between several Cocoon instances.
... or may be not. Have you used quartz + jdbc store configuration?
No, I don't actually (do not have any experience with jdbc store at all)
--
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
