[
https://issues.apache.org/jira/browse/OFBIZ-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043733#comment-14043733
]
Adam Heath commented on OFBIZ-1361:
-----------------------------------
Hmm, I see both sides of this coin.
In the entity engine, we have gone to create lengths to reduce the number of
methods, and provide single variants that have all options. This makes use of
the api much simpler, as only only need to remember each method, and the other
of parameters.
However, in framework/base, I could see just that component(or parts thereof)
being generally useful. Forcing ofbiz-only type semantics on it seems
heavy-handed.
Ideally, we wouldn't deprecate these methods, but have some other kind of
markup, maybe a @RecommendedVariant annotation.
used in places that have no
> Mark UtilDateTime.java deprecated methods as deprecated
> -------------------------------------------------------
>
> Key: OFBIZ-1361
> URL: https://issues.apache.org/jira/browse/OFBIZ-1361
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Reporter: Adrian Crum
> Assignee: Adam Heath
> Priority: Minor
> Attachments: UtilDateTime.patch
>
>
> Now that user-selected locale and time support has been added to the
> framework, it's time to start weeding out date/time code that doesn't use the
> Locale and TimeZone objects.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
