Right now, the default behavior of SchedulerFactoryBean is to start the scheduler when the framework comes up. The only way to change this would be subclass and having an empty method startScheduler{} in the subclass.
To avoid this, can a new attribute be added on SchedulerFactoryBean (say boolean startScheduler ) that has a default value = true. This way we won't have to subclass to change the startup behavior.
Shishir K Singh opened SPR-216 and commented
Right now, the default behavior of SchedulerFactoryBean is to start the scheduler when the framework comes up. The only way to change this would be subclass and having an empty method startScheduler{} in the subclass.
To avoid this, can a new attribute be added on SchedulerFactoryBean (say boolean startScheduler ) that has a default value = true. This way we won't have to subclass to change the startup behavior.
Thanks Shishir
Affects: 1.1 RC1