[richfaces-issues] [JBoss JIRA] (RF-12754) rich:validator message cannot be customized when using bean validation (via javax.faces.validator.BeanValidator.MESSAGE property)

[Nejc G (JIRA)]

     [ https://issues.jboss.org/browse/RF-12754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nejc G updated RF-12754:
------------------------

    Attachment: sample.rar


Hm I made sample and now I noticed you probably don't need it anymore... attaching it anyway since I've also noticed a4j:ajax works correctly for keyup event until blur happens (and msg gets replaced), so this is probably f:ajax thing.
                
> rich:validator message cannot be customized when using bean validation (via javax.faces.validator.BeanValidator.MESSAGE property)
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-12754
>                 URL: https://issues.jboss.org/browse/RF-12754
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-validators
>    Affects Versions: 4.3.0.CR1
>         Environment: Glassfish 3.1.2.2, jdk7u9
>            Reporter: Nejc G
>            Assignee: Brian Leathem
>         Attachments: sample.rar
>
>
> rich:validator clientside validation is ignoring javax.faces.validator.BeanValidator.MESSAGE property for messages. Standard validation without rich:validator works fine. Problem is there is no way to customize error (show label) hence making bean validation using this path nearly useless.
> I have the aforementioned property in a property file, configured to be used through locale-config line in faces-config.xml. The line reads:
> javax.faces.validator.BeanValidator.MESSAGE={1}: {0}
> and as mentioned rich:validator only outputs {0} (that is msg from bean validation). Seems to me it doesn't behave as configured.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira