[ot] Quartz ?

[Brent Putman]

On 3/12/15 12:18 PM, Marvin Addison wrote:
>
>     There's also the
>     newer native Java executor service pool type of approach.  Quartz
>     might
>     be overkill for this honestly
>
>
> +1
>
> I like Quartz -- it's great. But I've also dug under the hood enough
> to get a sense that it's big and complicated (RMI, property-based
> config, durable job/trigger storage). I would recommend using only if
> you have a clear use case.

That's definitely true, it has a lot of knobs and buttons and
capabilities. (I use the JDBC job store in a cluster configuration so
that my regular jobs execute just once, on whichever cluster node
happens to grab it first - so I get HA and don't tie the job to a
particular node).

But I think with just a simple config, RAM job store and Spring's
wiring support and defaults, it's probably pretty easy and manageable. 

Per my previous note, I do think the capability supported by their cron
trigger (vs say the simple interval repeating trigger) might be a nice
feature for some things (e.g. metadata reloading).  We currently can't
do that due to the limitations of Timer.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20150312/019f3fdd/attachment-0001.html