[patch available] [jira] Updated: (TRINIDAD-1538) Failing client side validation with some date patterns

[Cale Scholl <ca...@oracle.com>]

Howdy folks,

This patch has been available for a week. Could one of the Trinidad 
committers take a look?

Thank you,
Cale

Cale Scholl (JIRA) said the following" "On 7/31/2009 4:12 PM PT:
>      [ https://issues.apache.org/jira/browse/TRINIDAD-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Cale Scholl updated TRINIDAD-1538:
> ----------------------------------
>
>     Status: Patch Available  (was: Open)
>
>   
>> Failing client side validation with some date patterns
>> ------------------------------------------------------
>>
>>                 Key: TRINIDAD-1538
>>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1538
>>             Project: MyFaces Trinidad
>>          Issue Type: Bug
>>          Components: Components
>>    Affects Versions:  1.2.8-core
>>            Reporter: Lucas Satabin
>>         Attachments: 1.2.11.4-branch_dateFormat.patch, trunk_dateFormat.patch
>>
>>
>> Some patterns can not be validated on the client side, using a convertDateTime component:
>> Code to reproduce:
>> <tr:inputDate value="#{bean.value}">
>>     <f:convertDateTime pattern="yyMMdd" />
>> </tr:inputDate>
>> If you choose a date in the calendar, the formatting works fine in the text field. But when you submit, you receive an error message saying: valid example: 981124
>> This value obviously does not work either.
>> A workaround is to disable the client validation with <client-validation>DISABLED</client-validation> but we loose the client message when something is wrong (the valid example)
>>     
>
>