You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gabrielle Crawford (Resolved) (JIRA)" <de...@myfaces.apache.org> on 2012/02/07 03:35:00 UTC

[jira] [Resolved] (TRINIDAD-2213) DateFormatInfoScriptlet not getting 2 digit year start from same place as DateTimeConverter, using different values.

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

Gabrielle Crawford resolved TRINIDAD-2213.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.2-core
         Assignee: Gabrielle Crawford
    
> DateFormatInfoScriptlet not getting 2 digit year start from same place as DateTimeConverter, using different values.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-2213
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2213
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>            Reporter: Gabrielle Crawford
>            Assignee: Gabrielle Crawford
>             Fix For: 2.0.2-core
>
>
> The dateTimeConverter is getting the 2 digit year start from the request context, and it seems to correctly reflect the value in trinidad-config. 
> The DateFormatInfoScriptlet is getting the 2 digit year start from the localeContext, and it appears to be hard coded to 1950. This means that in the client converter 1950 is always used.
> Changing DateFormatInfoScriptlet  to get the 2 digit year start from the request context.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira