Project:
View Revisions: Issue #42035 | [ All Revisions ] [ Back to Issue ] | ||
Summary | 0042035: API change: make OBScheduler API simpler | ||
Revision | 2019-10-21 19:23 by caristu | ||
Description | The following methods for scheduling a job allows to specify the job class: - OBScheduler.schedule(java.lang.String, org.openbravo.scheduling.ProcessBundle, java.lang.Class<? extends org.quartz.Job>) - OBScheduler.schedule(org.openbravo.scheduling.ProcessBundle, java.lang.Class<? extends org.quartz.Job>) This does not make sense as the only job class used in core is DefaultJob and it does not exists any external class making use of those methods. Therefore this API can be limited to always use DefaultJob. Besides: - Method OBScheduler.schedule(java.lang.String, org.openbravo.scheduling.ProcessBundle) will no longer throw javax.servlet.ServletException as we are making use of a new dedicated TriggerGenerationException to handle trigger generation errors. This exception inherits from SchedulerException which was already being thrown by this method. - Method OBScheduler.format(java.util.Date) can also be removed as it is not used by other components. - AD_MESSAGE "TRIG_INVALID_DATA" is no longer needed |
||
Revision | 2019-10-21 19:22 by caristu | ||
Description | The following methods for scheduling a job allows to specify the job class: - OBScheduler.schedule(java.lang.String, org.openbravo.scheduling.ProcessBundle, java.lang.Class<? extends org.quartz.Job>) - OBScheduler.schedule(org.openbravo.scheduling.ProcessBundle, java.lang.Class<? extends org.quartz.Job>) This does not make sense as the only job class used in core is DefaultJob and it does not exists any external class making use of those methods. Therefore this API can be limited to always use DefaultJob. Besides: - Method OBScheduler.schedule(java.lang.String, org.openbravo.scheduling.ProcessBundle) will no longer throw javax.servlet.ServletException as we are making use of dedicated TriggerGenerationException to handle trigger generation errors. This exception inherits from SchedulerException which was already being thrown by this method. - Method OBScheduler.format(java.util.Date) can also be removed as it is not used by other components. - AD_MESSAGE "TRIG_INVALID_DATA" is no longer needed |
||
Revision | 2019-10-21 19:22 by caristu | ||
Description | The following methods for scheduling a job allows to specify the job class: - OBScheduler.schedule(java.lang.String, org.openbravo.scheduling.ProcessBundle, java.lang.Class<? extends org.quartz.Job>) - OBScheduler.schedule(org.openbravo.scheduling.ProcessBundle, java.lang.Class<? extends org.quartz.Job>) This does not make sense as the only job class used in core is DefaultJob and it does not exists any external class making use of those methods. Therefore this API can be limited to always use DefaultJob. Besides: - Method OBScheduler.schedule(String, ProcessBundle) will no longer throw javax.servlet.ServletException as we are making use of dedicated TriggerGenerationException to handle trigger generation errors. This exception inherits from SchedulerException which was already being thrown by this method. - Method OBScheduler.format(java.util.Date) can also be removed as it is not used by other components. - AD_MESSAGE "TRIG_INVALID_DATA" is no longer needed |
||
Revision | 2019-10-18 07:37 by caristu | ||
Description | The following methods for scheduling a job allows to specify the job class: - OBScheduler.schedule(java.lang.String, org.openbravo.scheduling.ProcessBundle, java.lang.Class<? extends org.quartz.Job>) - OBScheduler.schedule(org.openbravo.scheduling.ProcessBundle, java.lang.Class<? extends org.quartz.Job>) This does not make sense as the only job class used in core is DefaultJob and it does not exists any external class making use of those methods. Therefore this API can be limited to always use DefaultJob. Besides, this public method: - OBScheduler.format(java.util.Date) can also be removed as it is not used by other components. |
Copyright © 2000 - 2009 MantisBT Group |