Not sure if anyone would be interested in this but I implemented a new SchedulerService that pulls job info from the TurbineResources.properties instead of from the turbine database. Although it is not a real big deal it was important for my app. In my application I actually have 2 instances of turbine running which are meant to run on separate servers. Each server needs to have its own list of jobs to run (ie separate turbine databases) but I wanted both servers to use the same turbine user/security stuff (ie the same database). So with this new Scheduler this is possible. John -- ******************************** ** John Thorhauer ** [EMAIL PROTECTED] ** take a look at: ** http://tambora.zenplex.org ** http://www.zenplex.org ** http://www.zenplex.com ******************************** ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
