You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Markus Studer (JIRA)" <ji...@apache.org> on 2007/10/22 16:42:50 UTC

[jira] Updated: (OFBIZ-1363) UtilDateTime.toDate(int, int, int, int, int, int) does not initialise milisecond part of created date

     [ https://issues.apache.org/jira/browse/OFBIZ-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Markus Studer updated OFBIZ-1363:
---------------------------------

    Attachment: UtilDateTime.diff

Patch to set milisecond part of date to 0

> UtilDateTime.toDate(int, int, int, int, int, int) does not initialise milisecond part of created date
> -----------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-1363
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1363
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>            Reporter: Markus Studer
>            Priority: Trivial
>         Attachments: UtilDateTime.diff
>
>
> The public static java.util.Date toDate(int month, int day, int year, int hour, int minute, int second) method does not initialise the milisecond part of the created date predictably (uses the milisecond part of the current system time). This can lead to confusing results when comparing dates as the dates created with this method usually contain a milisecond part.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.