@Scheduled vs. Quartz JobExecutionContext

[famod]

Hi @mkouba (and others),

as I understand from https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/.40Scheduled.20annotation.20for.20Quartz.20Jobs/near/248450017, I have to use the programmatic API to JobExecutionContext.
Is that still the case?

What about a simple addition to ScheduledExcution, something like:

Optional<T> getContext(Class<T> contextClass);

For Quartz one could then call exec.getContext(JobExecutionContext.class).orElseThrow().[...].

Alternatively, there could be a simple, non-Optional getter only in QuartzScheduledExecution?

Our use case is storing some simple data with the job's JobDataMap and we really don't want to resort to the much more verbose programmatic approach...

Thanks!

[quarkus-bot[bot]]

/cc @machi1990, @mkouba

[mkouba]

Yes, we could make the QuartzScheduledExecution public and then add something like public <T> T unwrap(). So that you could do scheduledExecution.<QuartzScheduledExecution>unwrap().context.getMergedJobDataMap()...

@famod Could you pls file an issue?

[mkouba]

It's not and I don't think it should be the default...

[machi1990]

+1 something to be activated by a configuration? or to activate it all the time when the job store is a db one?

[famod]

I don't think it should depend on the store. Why shouldn't someone with the RAM store want to have the map stored between job executions? There is no real persistence due to the nature of the store, but still...

Ideally, one could control some details of the job config (like @PersistJobDataAfterExecution ) via an optional annotation, e.g. @QuartzJobConfig(persistJobDataAfterExecution = true, ...), next to @Scheduled.
Alternatively or additionally, there could be a global config flag. Depends on how efficient storing the map is for jobs that don't need it...

[famod]

Ideally, one could control some details of the job config (like @PersistJobDataAfterExecution ) via an optional annotation, e.g. @QuartzJobConfig(persistJobDataAfterExecution = true, ...), next to @Scheduled.

Or something like @QuartzJobClass(MyInvokerJob.class) and the custom class has to extend InvokerJob. In this case the user can add the annotation on his own.

[famod]

#26062