Inconsistent behavoir for JobDetail.isConcurrentExectionDisallowed()

[madness-inc]

Hi,
I tried to write a custom implementation of JobDetail, overriding isConcurrentExectionDisallowed().
In StdJDBCDelegate.insertJobDetail() the value is stored correctly in the database (setBoolean(ps, 6, job.isConcurrentExectionDisallowed()); ).

But when reading the JobDetail in StdJDBCDelegate.selectJobDetail(), the value previously written to the database is not considered, since JobDetailImpl implements isConcurrentExectionDisallowed() only based on the fact whether @DisallowConcurrentExecution is present.

This means the implementation of StdJDBCDelegate.selectJobDetail is hard-tied to the JobDetailImpl implementation of JobDetail, making it hard to use custom implementations for that interface that do not want to use @DisallowConcurrentExecution.

What's the developers perspective here?

Regards
Matthias

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.