You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-issues@incubator.apache.org by "Adam Winer (JIRA)" <ad...@incubator.apache.org> on 2006/12/13 00:31:23 UTC
[jira] Commented: (ADFFACES-316) Fix MVariableResolver to use
Calendar APIs instead of deprecated Date APIs
[ http://issues.apache.org/jira/browse/ADFFACES-316?page=comments#action_12457968 ]
Adam Winer commented on ADFFACES-316:
-------------------------------------
The patch as provided will generate different dates depending on the timezone of the server, I think.
> Fix MVariableResolver to use Calendar APIs instead of deprecated Date APIs
> --------------------------------------------------------------------------
>
> Key: ADFFACES-316
> URL: http://issues.apache.org/jira/browse/ADFFACES-316
> Project: MyFaces ADF-Faces
> Issue Type: Test
> Reporter: Yee-Wah Lee
> Priority: Trivial
> Attachments: ChooseDateRenderer.patch, trinidad-impl.patch, trinidad-impl.patch
>
>
> MVariableResolver is used by the ChooseDateRenderer tests to get min, max and midDate values. This is so the tests always generate the same output.
> However, the APIs used in the code are the deprecated Date constructors. I will replace them with the suggested GregorianCalendar equivalents.
> Patch file contains changes to MVariableResolver.java (new Calendar calls, and some import cleanups) and the corresponding chooseDate golden files
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira