[
http://jira.jboss.com/jira/browse/JBPM-1098?page=comments#action_12399275 ]
Alejandro Guizar commented on JBPM-1098:
----------------------------------------
Ronald, some of our customers have expressed concerns about this issue, so I want to
clarify the real nature of this problem. Please review the following description and tell
me if I'm missing something.
Durations in jBPM, as implemented by org.jbpm.calendar.Duration, are always treated as
milliseconds regardless of the unit of time that occurs in the process definition. Quoting
the aforementioned class, we have:
SECOND = 1000;
MINUTE = 60*SECOND;
HOUR = 60*MINUTE;
DAY = 24*HOUR;
WEEK = 7*DAY;
MONTH = 30*DAY;
YEAR = 365*DAY;
The problem is, not all months and years have the same length. Leap years are 366 days.
Months have between 28 and 31 days. Therefore, to accurately add months or years to a time
instant, the original unit of time must be preserved in order to determine how many days
to add, in relation to the month or year of the time instant.
Nevertheless, durations consisting of seconds, minutes, hours, days or weeks are NOT
affected, because these units always have the same length.
businesscalendar is unaware of leapyears
----------------------------------------
Key: JBPM-1098
URL:
http://jira.jboss.com/jira/browse/JBPM-1098
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Windows 2000, jdk 1.5.2_12
Reporter: Ronald van Kuijk
Assigned To: Ronald van Kuijk
Priority: Minor
Fix For: jBPM 3.3
businesscalendar of 65 years is 65/4 = 16 days short ( based on 1971).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira