This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes JSF and the fly likes Bean validation custom messages dont work Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » JSF
Bookmark "Bean validation custom messages dont work" Watch "Bean validation custom messages dont work" New topic
Author

Bean validation custom messages dont work

Jose Luis Mesa Munoz
Greenhorn

Joined: Nov 29, 2012
Posts: 1
First of all escuse me for my english. I have a problem with bean validation messages. I have ValidationMessages.properties, MessageResources.properties and in my .xhtml or in my ManagedBeans files i can access the keys... all is correct but when i put the


in my MessageResources bean Validations dont work well. This is my configuration:

faces-config.xml



The MessageResources



The .xhtml file



the property in my managedBean




the ValidationMessages.properties



Bean validation display my messages but not i this format javax.faces.validator.BeanValidator.MESSAGE={1}: {0}
where {1} is the label and {0} is the message. It only display the message with the key error.campoobligatorio=El campo es obligatorio

SOMEONE KNOWS WHY???
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 15960
    
  19

Welcome to the JavaRanch, Sr. Munoz! (¿Muñoz?)

I think your problem is:


Where it should be


The "#" triggers the EL processor.


Customer surveys are for companies who didn't pay proper attention to begin with.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Bean validation custom messages dont work
 
Similar Threads
.jsf page Display Issue with Spring, Primefaces and Tomcat 6 on Linux
In Rich Faces rich:panelMenu a4j:commandButton action not called
java.util.MissingResourceException
getting error when deploying web app in weblogic 10.0
App doesn't work