Fork me on GitHub
#admin-announcements
<
2015-12-20
>
sveri16:12:29

Hi, any opinions on quartzite here? Defining jobs and triggers seems like a lot of code to me. However, when I tried at-at it was like the recurring interval was not exact always

sveri16:12:40

Alternatives you would prefer?

sveri16:12:36

@larhat: Cool, didn't know that, thank you

larhat16:12:02

@jaen twarc is trying to address some problems of both immutant scheduling and quartzite

sveri16:12:52

But it looks already better than quartzite

jaen16:12:58

Yeah, I'm looking at the readme right now.

jaen16:12:12

Interesting, I thought immutant's scheduler works with clustered Wildfly no problem.

sveri16:12:35

@larhat: @jaen Hm, why cannot I pass state to immutants scheduler? At least the executing function can take state

sveri16:12:41

Or am I missing something?

larhat16:12:41

the key is "explicitly", I guess — jobs in immutant can’t take any arguments, so you have to wrap it in closure

jaen16:12:27

Yeah, but unless I'm misunderstanding something, how would you pass a DB connection for example? Wouldn't that mean it would have to be somehow persistable?