[richfaces-issues] [JBoss JIRA] Commented: (RF-8238) Calendar with datePattern from resourcebundle doesn't validate

[Andreas Schank (JIRA)]

    [ https://jira.jboss.org/jira/browse/RF-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12502045#action_12502045 ] 

Andreas Schank commented on RF-8238:
------------------------------------

This is a clone from RF-4791, because I couldn't reopen that issue.

I can reproduce this bug with 3.3.1.GA and 3.3.2.SR1.

When I try to get the pattern from a properties file I get the validation error as printed above (but with an empty example), when I hardcode it or get the pattern throud a bean-getter-Method everything works fine.

I use Richfaces with the Briidge 1.0.0.CR2 on JBoss 5.1.0.GA with Liferay 5.2.3.
The server is started with "-Duser.language=en -Duser.country=US" the default message bundle does not include the pattern, only the _de and _en bundles include it.


> Calendar with datePattern from resourcebundle doesn't validate
> --------------------------------------------------------------
>
>                 Key: RF-8238
>                 URL: https://jira.jboss.org/jira/browse/RF-8238
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.2.2
>            Reporter: Andreas Schank
>            Assignee: Alexander Dubovsky
>             Fix For: 3.3.0
>
>
> See also:
> http://www.jboss.com/index.html?module=bb&op=viewtopic&t=143930
> I use:
> <rich:calendar value="#{person.birthDate}" datePattern="#{messages['datepattern']}/>
> The date *is* formatted according to the pattern, but on submitting the form, the validation fails:
>  '04-12-1968' could not be understood as a date. Example: 29-10-2008
> Note: the example also uses the correct datePattern
> If I hardcode the pattern in the template (datePattern='dd-MM-yyyy'), the validation succeeds (but then the pattern is not localized anymore).
> I tried a4j:loadBundle, and referencing that instance (this was a suggestion from the forum entry). It resulted in the same error message.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira