NOTE: client code is responsible for making sure a job with the name identified by the parameter StandardSettings.SCHEDULE_NAME in the parameter provider
does not already exist in the quartz scheduler.
Does this method belong in ChartBeansGeneratorUtil? ChartBeansGeneratorUtil may be more of a convenience for
executing the default ActionSequence, if this is to hold true, this method probably needs a new home more central
to the ChartBeans code.