Wrong list? Anyway, I'm not sure it's worth removing if it's a configurable option. From a Grails perspective, it's so easy to install the Quartz plugin that it's actually a reasonable option for users. I'm not saying that anyone *would* use it, but it would be there. Then again, I don't think it matters a whole lot :) So if you want to remove it, I'm fine with that too.
Cheers, Peter 2008/7/24 Les Hazlewood <[EMAIL PROTECTED]>: > We have an optional dependency on Quartz at the moment for proactive session > validation when using our enterprise Sessions. > > Naturally our SessionValidationScheduler is an interface, and we have a > QuartzSessionValidationScheduler. > > But I recently (about 3 months ago?) added an > ExecutorServiceSessionValidationScheduler which uses the JDK's built-in > ExecutorService to validate sessions at a user-defined interval. This is > our default implementation used in our code for automatic startup. > > This makes the Quartz implementation sort of an orphan at the moment - we > don't use it in our code or in any of our sample apps. It is essentially > only there if an end-user explicitly configures a > QuartzSessionValidationScheduler, and I honestly don't think anyone does > that. Almost any session validation configuration is done through > convenience passthrough properties (setValidationEnabled, > setValidationInterval, etc). > > Any objections of me removing it (and the quartz.jar dependencies) from the > project? >
