Method Scheduler for Java

A robust scheduler component that allows developers to execute methods on Java objects asynchronously and/or repeatedly.

Date Posted: May 28, 2004

Overview Requirements Download FAQs Forum Reviews 1. Can I use Method Scheduler for Java (MS4J) to execute a task at a specified future point in time? 2. Can I have MS4J save the list of tasks currently scheduled? 3. Can I have MS4J read its properties from a PropertyResourceBundle present in classpath? 4. Can I have MS4J automatically retry failed tasks? 5. Why is MS4J better than the Timer facility of Java? 1. Can I use Method Scheduler for Java (MS4J) to execute a task at a specified future point in time? Not really. You can execute a task X number of seconds from now, but not at 5:00 pm on August 12, 2006. If there is enough demand, we will make this feature available in the future Back to top 2. Can I have MS4J save the list of tasks currently scheduled? No. MS4J was meant to be a lightweight scheduler with no persistence. Again, if there is enough demand, we will add this feature. Back to top 3. Can I have MS4J read its properties from a PropertyResourceBundle present in classpath? Yes. Back to top 4. Can I have MS4J automatically retry failed tasks? Yes. Back to top 5. Why is MS4J better than the Timer facility of Java? MS4J has a configurable thread pool and will not overwhelm your machine when it has a lot of work to do. It is also easier to add MS4J to your existing code, since you don't need to rewrite classes in order to make them execute asynchronously. Back to top