Title: Message Title
|
|
1. The Job A depends on Job B sounds a bit overkill, you would hope we wouldnt have to add in jobs that had this behaviour/requirement.
2. We would like to design things that you wouldnt have to 'disable' access to the rest of the system just cause some 'scheduled' jobs are running - they tend to run 'out of business hours' anyway so this is a low priority for me unless theres a clear need for it.
They key things around the 'scheduling' work are:
1. Configure spring scheduling to work with application (done) 2. Persist the task/job information in tenant database to allow differ jobs per tenant and record of jobs available (done i think) 3. Abliity to 'update/adjust' existing job information (when it is run, should it be run (enabled/disabled) etc) 4. Ability to add/remove jobs dynamically 5. Should be able to optionally schedule when reports run for example, 6. Ability to trigger a job on demand (through UI/ API ) to run now 7. API around scheduling capabilities to expose functionality for people to build UI or other integrations
|
|
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues