|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is duplicated by:
|
|
QUARTZ-505
org.quartz.CronTrigger.setCronExpress...
|
|
|
|
Related
|
|
This issue relates to:
|
|
QUARTZ-353
Correct JavaDoc in CronExpression
|
|
|
|
|
|
|
|
The CronExpression parsing appears to ignore any characters after a valid expression. For example this test currently succeeds:
assertEquals(
new CronExpression("0 15 10 5 * 5 2005").getExpressionSummary(),
new CronExpression("0x 15y 10z 5C * 5C 2005x").getExpressionSummary());
Interestingly, new CronExpression("0x 15y 10z 5C *X 5C 2005x") also passes parsing, but MONTH is expanded to 1,2,3,4,5,6,7,8,9,10,11,12, so it looks like an extra char after a "*" has a slightly different impact.
|
|
Description
|
The CronExpression parsing appears to ignore any characters after a valid expression. For example this test currently succeeds:
assertEquals(
new CronExpression("0 15 10 5 * 5 2005").getExpressionSummary(),
new CronExpression("0x 15y 10z 5C * 5C 2005x").getExpressionSummary());
Interestingly, new CronExpression("0x 15y 10z 5C *X 5C 2005x") also passes parsing, but MONTH is expanded to 1,2,3,4,5,6,7,8,9,10,11,12, so it looks like an extra char after a "*" has a slightly different impact. |
Show » |
| There are no comments yet on this issue.
|
|
Bug
Open
