Title:
[ANeff] Bug for: startdate/enddate vs exclude wrt year format in neo-cron.xml
| View in TrackerStatus/Resolution/Reason: Closed/Withdrawn/NotABug
Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)
Created: 01/27/2013
Components: Scheduler
Versions: 10.0
Failure Type: Unspecified
Found In Build/Fixed In Build: Final /
Priority/Frequency: Trivial / Very few users will encounter
Locale/System: English / Win All
Vote Count: 0
cfschedule stores 2-digit years as 4-digit years for startdate and enddate, but not for exclude.
Repro:
1) Run <cfschedule action="update" task="myTask" url="http://a" interval="daily" startdate="1/1/13" exclude="1/15/13" enddate="1/31/13" starttime="00:00" endtime="23:59" />
2) Open neo-cron.xml
Actual Result:
<var name='start_date'><string>1/1/2013</string></var>
<var name='exclude'><string>1/15/13</string></var>
<var name='end_date'><string>1/31/2013</string></var>
Expected Result:
<var name='start_date'><string>1/1/2013</string></var>
<var name='exclude'><string>1/15/2013</string></var>
<var name='end_date'><string>1/31/2013</string></var>
The 1/15/13 should be 1/15/2013.
Even if exclude treats '13' as '2013' (haven't tested this - b/c currently exclude doesn't properly support *TIME*), fixing this now may prevent a future bug once the other exclude-related bugs that I've reported are fixed.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3490519
External Customer Info:
External Company:
External Customer Name: itisdesign
External Customer Email:
Attachments:
Comments: