there's no magic ... what the Scheduler does is call to CommandsManager.getInstance().getCommand(catalogName, cmdName);
>From the times in the screenshot, I guess you have created the "commands" node and the catalog and the command underneath at the same time. The "commands" node and its children will not be observed until the next restart of the server so if you have not restarted the command will not be found. Another possibility is that you have the "books" catalog already defined in some other module ... if that is the case then only the catalog that is found first will be used. They are not additive. HTH, Jan On Thu, 2010-01-14 at 10:21 -0600, Rakesh Vidyadharan wrote: > I am trying to schedule an updater command using the scheduler module, > but it fails with an error that it cannot find the command specified. > I am not too sure about how to go about configuring either, but these > are what I have: > > 1. http://sptci.com/uploads/magnolia/command.png – Command > configuration in our books module > 2. http://sptci.com/uploads/magnolia/schedule.png – Scheduler > configuration for the above command > > The error message I get is: > > 2010-01-14 10:10:00,058 ERROR > info.magnolia.module.scheduler.CommandJob : can't find command > updateData for job in catalog books > > Can someone guide me (I could not find anything on the documentation > site) on how to configure commands and schedules. I think the main > issue as it stands now is what the catalog means in the scheduler > context. > > Thanks > Rakesh > > > ______________________________________________________________________ > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
