I understand your point :) But sometimes when some change is made in the ejb module say a Session bean and the jar is re deployed to JBoss through Netbeans 6.1, it will not deploy the new jar for no obvious reason. Then we have to stop JBoss, remove the previous jar file from deploy folder manually. Start JBoss again and then deploy the modified jar through Netbeans. With this Scheduler implementation, the above procedure will not work as JBoss is depending upon the jar before it starts. That is why I wanted to find some way to avoid this dependency. Now I guess we will just have to make sure that the jar file is always in the deploy folder before starting JBoss. Thanks a lot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145422#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...