Hi Dan, Thanks for the explanation. I will look at your suggestions tomorrow.
Kind regards, Sander > On 30 Sep 2014, at 18:31, Dan Haywood <[email protected]> wrote: > > Hi Sander, > > There's not a lot of value-add in that isis-module-scheduler add-on, but > what it DOES do is to show what a background job (that can be run by > Quartz) should be implemented as (in order to set up an Isis session etc). > > The other side of the equation is in setting up the jobs and persisting > them into some sort of JobStore. Quartz already has its API there, but the > integration doesn't try to provide any deeper integration with Isis. In > particular, the module does NOT try to map jobs as Isis-managed entities. > > If you look at the todoapp archetype (1.6.0) you'll see that the app it > generates has a scheduler already configured, so you could take a look at > that. The jobs are set up in the @PostConstruct and are just hard-coded, > and stored in memory. > > Hope that helps, let me know... > > Cheers > Dan > > > > On 30 September 2014 16:52, Sander Ginn <[email protected]> wrote: > >> Hi, >> >> I am attempting to implement the scheduler plugin [1] but am running into >> problems. >> My understanding is that I need a @PostConstruct on my initializeJobs() in >> order to automatically start the scheduler, but the example on GitHub says >> otherwise and I fail to see how to ensure that the plugin is properly >> configured. >> >> Could you please explain how to do this the right way? >> >> Kind regards >> Sander >> >> [1] https://github.com/danhaywood/isis-module-scheduler < >> https://github.com/danhaywood/isis-module-scheduler>
