Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
5.8.0
-
None
Description
We currently create a JobSchedulerStore by looking for the KahaDB implementation which means another store can't implement one itself and provide that instead of always needing the KahaDB implementation always.
We can use the PListStore approach and check if the PersistenceAdapter implements JobSchedulerStore before we jump into the KahaDB lookup code.
It would be nice if the details of directory etc could be removed from BrokerService and be configured via the persistence adapter but for now we probably don't want to break backwards configuration compat.
Attachments
Issue Links
- supercedes
-
AMQ-3024 Scheduler should support non-Kaha persistence
- Resolved