For our CAS deployment, we have reorganized our Spring contexts such that all Quartz-driven scheduled tasks live in a scheduledTasks.xml that contains jobs for the following:
- Periodic cleaning of JPA ticket registry - Periodic purging of JPA-backed Inspektr audit data (anything older than 200 days in our case) - Periodic reload of JPA-backed service registry I would imagine many folks would have a need for these, and possibly more, scheduled tasks. I think organizing all scheduled tasks in one Spring context file is helpful for a number of reasons. Is there interest in refactoring the CAS 3 scheduled tasks into a single context file? Additionally, we'd be interested in donating our AuditTrailJdbcCleaner class which deletes audit data older than some cutoff age. M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
