I replied too soon to the previous email before seeing Thomas' comments. Yes, I see that quartz is quite popular. I am not sure it is worth building out the UI other than to maybe provide simple start/stop scheduler service and display current jobs and next run times. I have that much working already :-)
- Jeff On 10/15/2018 12:17 PM, Thomas Vandahl wrote: > Hi Jeff, > > On 12.10.18 02:32, Jeffery Painter wrote: >> Looking at the startup logs, it says it is using a RAMJobStore store >> which is not persistent. Does the new Quartz scheduler not support >> persisting job entries? The log tells me no user-supplied config was >> found, so I guess there is some way to configure it further :-) > The Quartz scheduler basically runs "side-by-side" with Turbine. There > is just the bridge between Turbine scheduled jobs and the Quartz > interfaces. Turbine no longer provides tools for persisting jobs. Quartz > comes with several JobStores that you can configure to your liking. See > http://www.quartz-scheduler.org/documentation/quartz-2.2.x/configuration/ConfigJobStoreTX.html > for an example. > > As Georg already pointed out, the Quartz scheduler tries to load > /quartz.xml from the class path. Most of the parameters can also be set > in the component configuration of the Avalon service. See > http://turbine.apache.org/fulcrum/fulcrum-quartz/ and especially > http://turbine.apache.org/fulcrum/fulcrum-quartz/configuration.html > >> Once I figure it all out, I was going to put together a simple Job >> Manager UI in the flux package similar to the way we have the user >> manager. I think it would be a nice addition (provide basic >> functionality, start/stop scheduler, add/remove jobs, check current job >> status). Let me know what you think. > You should be aware that Quartz is much more popular than Turbine :-) > Just google for "quartz scheduler gui" There are several hits, both, > free and commercial. Look there first and then decide if rolling your > own is worth the effort. > >> Also, I would be happy to write this all up when I get it working and >> add to the site docs (the schedule docs there now only apply to T-2.3.x >> version I believe). > That would be great! These days, good documentation is as important as > good code, if not more important. > > Bye, Thomas >
signature.asc
Description: OpenPGP digital signature
