It fixes problem #109 .
The problem was the lack of the job's name.
When no jobs name is defined, quartz sets a random name. Then. when the scheduler is fired the trigger is related to the jobs name. As the trigger is set once on reschedule it does not use the job random job's name.
Fixes #109
How Has This Been Tested?
We did a unit test to cover this beahvior.
Checklist
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have added tests to cover my changes
[ ] I have made corresponding changes to the documentation
Disclaimer
By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement
Description
It fixes problem #109 . The problem was the lack of the job's name. When no jobs name is defined, quartz sets a random name. Then. when the scheduler is fired the trigger is related to the jobs name. As the trigger is set once on reschedule it does not use the job random job's name.
Fixes #109
How Has This Been Tested?
We did a unit test to cover this beahvior.
Checklist
Disclaimer
By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement