You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Adrian Crum (JIRA)" <ji...@apache.org> on 2015/09/21 18:05:04 UTC

[jira] [Commented] (OFBIZ-6647) Refactoring to consolidate different Calendar implementations

    [ https://issues.apache.org/jira/browse/OFBIZ-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900893#comment-14900893 ] 

Adrian Crum commented on OFBIZ-6647:
------------------------------------

ICU4J was chosen for 2 reasons:

1. Better calendar selection (Java has only 2 if I recall correctly).
2. Time zone data can be updated easily by downloading the latest library version (versus waiting for the next Java revision).

ICU4J is used as the default Calendar implementation in OFBiz. The java.util.Calendar class is used where an API requires one.


> Refactoring to consolidate different Calendar implementations
> -------------------------------------------------------------
>
>                 Key: OFBIZ-6647
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6647
>             Project: OFBiz
>          Issue Type: Improvement
>    Affects Versions: Upcoming Branch
>            Reporter: Michael Brohl
>            Assignee: Michael Brohl
>            Priority: Minor
>             Fix For: Upcoming Branch
>
>
> This came up in reference to [6594|https://issues.apache.org/jira/browse/OFBIZ-6594]:
> Piere Smits: "Currently we are using 'import com.ibm.icu.util.Calendar' at various places. But we're also using 'java.util.Calendar' at other places.
> Better is it to make a choice for consistency."
> We should fisrt analyze the usage of different implementations and the impact of replacing one with the other (e.g. what's the difference of these implementations).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)