The JRE provides TimerTask, but it's a huge pain in the ass to use with CFML because the Java-to-CFML bridges are laughably weak. OpenSymphony has Quartz (which is awesome), but being Java, it suffers the same problem. Yes, even with the bennies CFGroovy offers in the Java space.

CFSCHEDULE is lame, especially on ColdFusion with it's 61 second frequency limit. Even with an optimal implementation the entire mechanism is flawed because it's a) stuck with equal iteration periods, and b) can only invoke URLs. Every distinct task requires punching a hole in your URL security, making a UI-layer facade for the task, etc.

The Java mechinisms are much better because they stay in-JVM (i.e., don't go through HTTP), but the statelessness of CFCProxy is a huge burden. You can't access already-instantiated CFCs, which means you end up writing a massive pile of custom facade/proxy code to interface with your already-running business model.

The natural solution, of course, is implementing cron in CFML. It allows you to pay either the HTTP or CFCProxy cost exactly once, as well as have cron's incredibly flexible scheduling format. This fact, in it's various manifestations, drives me to drink rather ridiculous amounts.

The flip side, of course, is the dynamic reloading nature that CFML servers offer. I simply cannot understand why other JVM frameworks have not copied this feature. The complete avoidance of all the JVM restarts and classloading hell is a benefit worth enormous sacrifice. Which, I suppose, is why I write CFML both for my salary and for personal projects.

Am I the only one who thinks this is a problem? With both CFML and other JVM frameworks.