Here are some ideas that I have atm
1. Serialize the in-memory data structures used by quartz and reload
them after server startup.
(may require a separate partition to store)
2. Use an embeddable RDBMS. In this case quartz can directly store data
using its inbuilt JdbcStore.
(This may be the last and least preferable option )
--
Kiran Ayyagari
Kiran Ayyagari wrote:
hi guys,
I have been working on finding ways to integrate quartz into the
server and mainly on the feature to store the
quartz scheduling data a.k.a Quartz LDAP store.
Currently quartz has two kinds of stores, In-memory and RDBMS.
Quartz uses 12 tables!! to store data in
RDBMS (attached the pdf of the ER diagram)
The LDAP store is not a separate store but an interface to store
the data in the given partition like
ou=system. How can we represent this relational data per row in a
single LDAP entry?
thoughts?
