Issue Details (XML | Word | Printable)

Key: GLASSFISH-18537
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: mtaube
Reporter: myfear
Votes: 2
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

Validation Message Bundles don't get resolved in correct language

Created: 21/Mar/12 12:18 PM   Updated: 19/Feb/13 09:42 PM   Resolved: 19/Feb/13 09:42 PM
Component/s: bean-validator
Affects Version/s: 3.1.2_b22
Fix Version/s: 3.1.2_b05

Time Tracking:
Not Specified

File Attachments: 1. Zip Archive constraints.zip (27 kB) 21/Mar/12 12:18 PM - myfear

Environment:

GlassFish Server Open Source Edition 3.1.2 (build 22)
Name of the Operating System: Windows 7
Binary Architecture name of the Operating System: amd64, Version: 6.1
Java HotSpot(TM) 64-Bit Server VM Vendor: Sun Microsystems Inc. Version: 20.1-b02


Tags:
Participants: Aquillo, mtaube, myfear and shreedhar_ganapathy


 Description  « Hide

Using Bean Validation constraints like the following including providing a message property
@NotNull(message = "{Album.name.notNull}")

and having the default ValidationMessages.properties
packaged with only one language specific version (e.g. ValidationMessages_de.properties) leads to wrong locale being used for clients which use other than the language specific locale.

Example attached:
visit with a en/en_US browser setting
http://localhost:8080/constraints/
<= create album leads to a German message to be displayed.