OK, so the first time this method is called in a Job, it will set the "date" static variable. If it has already been set, the date being passed in ("sourceDate") does nothing to the "date" variable. Then we add 5 minutes to the "date" variable. This means that every time this method is called, 5 minutes will be added to the "date" variable which is maintained as a static variable. This was the logic of the original code I sent.
The next bit was a bit of a quick fix to keep it to the same day. This is an ideal solution, but works in your scenario. To make sure that the day remains the same, we use the "sourceDate" param value and check its day of the week against the updated "date" variable's day of the week. If they are different, we subtract 1 day from the updated "date" value.
As I said, this is not perfect. If you send through a different date in subsequent calls, it will cause 1 day to be removed from the output date. As such, I have updated this below to give a better solution in case your date does change. The "initialDay" variable will now store the very first day of the week supplied during the run of the job.
public class DateIteration {
private static Date date;
private static int initialDay;
public static Date iterateDates(Date sourceDate, int minutesToAdd) {
if(date==null) {
date = sourceDate;
initialDay = routines.TalendDate.getPartOfDate("DAY_OF_WEEK", sourceDate);
}
date = routines.TalendDate.addDate(date, 5, "mm");
if(initialDay!=routines.TalendDate.getPartOfDate("DAY_OF_WEEK", date)){
date = routines.TalendDate.addDate(date,-1,"dd");
}
return date;
}
}
