Unless you feel it is adequately tested and documented and can be included in the 4.0.5 release. I have yet to hear anything on the subject from you. I for one am not thrilled with a ResourceAdapter that, regardless of whether there are any deployed endpoints or not, decides to fire up a default scheduler. A scheduler that is a) Undocumented b) Could conflict with any existing schedulers that people may be running in previous release c) Consumes resources without even an attempt to be integrated with our existing thread pools etc, etc I mean really dude, you are treating this RAR as the 'holy grail' of Timer integration when all it really does, stupidly might I add, is register an MDB listener for a single Quartz job. So I guess if I am intersted in listening to say...3 jobs...do I need 3 endpoints? How about 10? What if I never deploy an endpoint at all...do I still want the Scheduler up and running....doing nothing but showing up in a ThreadDump. How about support, have they been told about the adapter and what it means when it starts showing up in profiling info or clients, god forbid, actually try and use it? At the very least, I think for 4.0.5, the RAR should go in the docs directory giving the client a choice if they want to deploy the adapter or not. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957390#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...