I have same problem. Did you solve the problem?
Something to consider is packaging the scheduler mbean *within* the ear as a sar. (Coincidentally, I just did this 5 minutes ago.)
All you have to do is:
Build a .sar file that includes the schedulable class and a jboss-service.xml file in the META-INF directory. This file can look exactly like scheduler-service.xml.
Include a jboss-app.xml file in the META-INF of the ear. The format of the file is:
On my system with this setup, Jboss deploys the EJBs before the scheduler service and everything works great.
That worked for me too. But there is one disadvantage: you cannot change the scheduler config at runtime.
I created sar file. But still i have problem. I am attaching my jboss
<?xml version="1.0" encoding="UTF-8"?>
<!-- classpath codebase="lib" archives="*" -->
All right, I packaged the Scheduler service inside as a .SAR and it works great. The scheduable class is actually still in the main application JAR, but it looks like SAR format is honoring the Class-Path: in the manifest.