I had talked to Bill about this prior to him writing the adapter. I had assumed it was going in Varia as it was unproven, utested etc, etc. I can get stuff ready for the 4.0.5 release.
The main issue is that we now have like 6 different types of timer services.
java.util - many different build on top of this
jboss util timed queue
There was already brought up in this timer unification thread:
The quartz api as one we expose seemed huge and at this point should only be an implementation detail. We need a full discussion of a timer service with support for txns, persistence, clustering, etc.
Yes, want me to link the issue in JIRA, and we treat it as the 'unification' of all of this stuff?