Vadim Gritsenko wrote:
[EMAIL PROTECTED] wrote:
> Modified: cocoon/branches/BRANCH_2_1_X/src/blocks/cron/java/org/apache/cocoon/components/cron/QuartzJobScheduler.java
> ==============================================================================
> --- cocoon/branches/BRANCH_2_1_X/src/blocks/cron/java/org/apache/cocoon/components/cron/QuartzJobScheduler.java (original)
> +++ cocoon/branches/BRANCH_2_1_X/src/blocks/cron/java/org/apache/cocoon/components/cron/QuartzJobScheduler.java Wed Sep 22 07:42:00 2004
> @@ -547,6 +555,7 @@
> > jobDataMap.put(DATA_MAP_NAME, name);
> jobDataMap.put(DATA_MAP_LOGGER, getLogger());
> + jobDataMap.put(DATA_MAP_CONTEXT, this.applicationContext);
> jobDataMap.put(DATA_MAP_MANAGER, this.manager);
> jobDataMap.put(DATA_MAP_ENV_CONTEXT, this.environmentContext);
> jobDataMap.put(DATA_MAP_RUN_CONCURRENT, new Boolean(canRunConcurrently));
You'll also have to remove this entry from jobDataMap when Quartz is about to write it into the database. See QuartzDriverDelegate, methods removeTransientData() and selectJobDetail().
O, good one, thanks :-) Will take care of this.
-- Unico
