Issue:
I’m using Jmix add-on modules with separate databases configured via Additional Stores.
After adding the quartz-job screen to an add-on module, Quartz jobs still use the primary database instead of the add-on’s designated store.
Current Implementation:
I’ve extended the JobModelBrowse class to add custom logic, and I’m successfully using the digitalDataManager (configured with @Qualifier(“digital”)) for other operations:
Code Example:
@Autowired
@Qualifier(“digital”)
private DataManager digitalDataManager;
Question:
How can I configure Quartz jobs in add-on modules to use their respective Additional Stores rather than the main database?
configuration file:-
digital.datasource.jdbc-url=jdbc:postgresql://localhost:5432/postgres?currentSchema=modularization
digital.datasource.username=postgres
digital.datasource.password=postgres
digital.datasource.driver-class-name=org.postgresql.Driver